Re: [jboss-as7-dev] Consolidating ports under 80/443
Web sockets are as good as anything else, as long as our implementation is solid. I
intend to investigate a websocket-based Remoting back end. The only question would be:
should protocols run on Remoting or directly over web sockets, or both? I think the
answer will depend on what kind of security and performance requirements each protocol
has.
--
- DML
On May 18, 2012, at 12:24 PM, Scott Stark <sstark(a)redhat.com> wrote:
How does control of processing the socket transfer from web tier to
the associated service executor/thread pool? Won't there need to be some kind of
integration with the upgrade processing?
----- Original Message -----
From: "Remy Maucherat" <rmaucher(a)redhat.com>
To: jboss-as7-dev(a)lists.jboss.org
Sent: Friday, May 18, 2012 9:35:35 AM
Subject: Re: [jboss-as7-dev] Consolidating ports under 80/443
On Fri, 2012-05-18 at 11:36 -0400, Bill Burke wrote:
> I'm not talking about websockets. There's a bunch of subsystems that
> have their own proprietary protocols i.e. HornetQ has their superfast
> protocol as well as STOMP, neither of which use HTTP or WebSockets.
> THey could use HTTP Upgrade to connect, then just take over the socket
> to do with whatever they wanted.
WebSockets does an upgrade, so ...
--
Remy Maucherat <rmaucher(a)redhat.com>
Red Hat Inc
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev