[jboss-jira] [JBoss JIRA] (WFLY-2055) Centralize and organize I/O-related options into I/O subsystem

[Jason Greene (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Greene updated WFLY-2055:
-------------------------------

    Fix Version/s: 8.0.0.Final
                       (was: 8.0.0.CR1)

    
> Centralize and organize I/O-related options into I/O subsystem
> --------------------------------------------------------------
>
>                 Key: WFLY-2055
>                 URL: https://issues.jboss.org/browse/WFLY-2055
>             Project: WildFly
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Remoting, Web (Undertow)
>            Reporter: David Lloyd
>            Assignee: Tomaz Cerar
>             Fix For: 8.0.0.Final
>
>
> Centralize all the I/O related options into the I/O subsystem schema.  This includes all XNIO Options, and also includes moving all XNIO worker configuration into the I/O subsystem to be referenced.
> The I/O subsystem should define types for each I/O option including (but not limited to):
> * send and receive buffer sizes
> * TCP nodelay setting
> * TCP keepalive
> * IP TOS
> * Server socket backlog
> * Server connection limit low/high water mark
> * etc.
> Also there should be types defined for:
> * XNIO worker thread count
> * XNIO worker thread stack size
> * XNIO worker thread priority
> * etc.
> Systems which define I/O entities will reference these types by including the allowed/relevant option types into their schema like the threads subsystem does for thread pool types.
> Systems presently defining workers should instead reference a worker defined in the I/O subsystem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira