Unless you are going to need more than one web container i really don't see the reason to use Apache HTTPD as a reverse proxy, provided that you have installed and are using the APR connector. As for the anwser to the question "how do you achieve proxying of websocket communication" i think there is no standard way yet. Keep in mind users are probably going to run into problems with Websockets if they are behind a firewall, web proxy etc. Unfortuantely websockets are great but are not mature yet.
On Tue, Sep 18, 2012 at 10:47 PM, sfwicket <li...@bgb.net> wrote: > > Assuming you mean you can't use mod_jk with a WebSocket app... > > More generally speaking, what is the Best Practice for configuring a > production environment stack utilizing a Tomcat Web App which uses > WebSockets? Load Balancer, Apache, Tomcat - and specifically - the proxying > of traffic on port 80. Should Tomcat just be run on port 80? If not, how is > the proxying achieved to allow WebSocket traffic alongside of static Apache > traffic and normal Java traffic on the same port? > > Thanks! > > > > > -- > View this message in context: > http://tomcat.10.n6.nabble.com/Tomcat7-WebSocket-mod-jk-tp4986848p4986853.html > Sent from the Tomcat - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
