[
https://issues.jboss.org/browse/WFLY-3588?page=com.atlassian.jira.plugin....
]
Tomaz Cerar commented on WFLY-3588:
-----------------------------------
go to properties type of config options than...
Not ideal for our model driven management, but probably only way we can go with.
what did you have in mind
something like
<http-listener name="default">
<option name="spdy-enabled" value="true" />
<tcp-option name="TCP_NODELAY" value="false" />
</http-listener>
or even more granular, by defining option class?
Undertow subsystem should support arbitrary options
---------------------------------------------------
Key: WFLY-3588
URL:
https://issues.jboss.org/browse/WFLY-3588
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web (Undertow)
Reporter: Stuart Douglas
Assignee: Tomaz Cerar
At the moment all well known options are hard coded in the schema. We should also support
dynamic options where the class name is specified. This will allow the use of user defined
options.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)