I have submitted a PR for this:
https://github.com/wildfly/wildfly/pull/4447
This does not attempt to address EJB and remote naming, I will get to
them in a separate PR once this one is merged.
Unfortunately there is no way to move to single port by default without
breaking JBoss tools (and all older clients) backwards compatibility,
although they will still work if you install the remote connector.
Stuart
Stuart Douglas wrote:
This is now mostly ready to go, however it will require some other
projects to release before I can submit a pull request.
There also appears to be a SSL bug in XNIO upstream which is causing a
test failure that will also need to be resolved before this can be merged.
Stuart
Stuart Douglas wrote:
> Ok, I will change this again, and this this will probably be ready for
> review.
>
> I have also added some additional headers to the handshake to make sure
> both client and server are using the correct protocol, basically I took
> the web socket handshake from the websocket v13 spec but with different
> header names and a different magic number.
>
> Stuart
>
> Jason Greene wrote:
>> On Apr 2, 2013, at 4:42 AM, Darran
>> Lofthouse<darran.lofthouse(a)jboss.com> wrote:
>>
>>> Just thinking would http-remoting and https-remoting be better names
>>
>> Sounds good to me.