Meaningless Drivel is fun!
The moose likes Tomcat and the fly likes Want opinions on Tomcat / Websockets integration. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Tomcat
Bookmark "Want opinions on Tomcat / Websockets integration. " Watch "Want opinions on Tomcat / Websockets integration. " New topic

Want opinions on Tomcat / Websockets integration.

Roger F. Gay
Ranch Hand

Joined: Feb 16, 2007
Posts: 408
A year or so after creating my own websocket server, I wrote a blog article expressing my thoughts on Websocket / Tomcat server integration. (WebSockets with Apache Tomcat and HLL) I lean heavily toward not really caring much. Don't get me wrong, I use Tomcat a lot. It's one of my favorite things. I pointed out in the article that the Websocket connection is completely separate from any HTTP connection you make to get your Web Page or whatever. It doesn't matter where the Websocket machine is relative to the HTTP server.

But I'm starting to have some second thoughts and since I've noticed so many people asking about Tomcat / Websockets, I'm wondering if others have already formulated another view. If I for some reason wanted my Websocket related code interacting with app code developed with servlets under Tomcat, then I could easily do so by putting at least one object in the scope of the Tomcat application that could communicate with the Websocket application ... but that's already starting down the slippery slope of integration. ON the other hand, why not just use the Websocket connection ... or ...

Any general thoughts on the subject, pro or con?

Correlation does not prove causality.
I agree. Here's the link:
subject: Want opinions on Tomcat / Websockets integration.
It's not a secret anymore!