Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
From: bugzilla@apache.org
To: dev@tomcat.apache.org
Subject: DO NOT REPLY [Bug 51181] Add support for Web Sockets
Date: Sun, 08 Jan 2012 22:38:44 +0000
Message-ID: <bug-51181-78-pC4l6wBBrW@https.issues.apache.org/bugzilla/>
In-Reply-To: <bug-51181-78@https.issues.apache.org/bugzilla/>
References: <bug-51181-78@https.issues.apache.org/bugzilla/>
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=51181

--- Comment #24 from goberman@msn.com 2012-01-08 22:38:44 UTC ---
I actually played with Jetty WebSocket API last Friday and was able to embed it
into Tomcat quite easily. The only issue is that it has to be on a separate
port.
As I mentioned before, it would be a good selling point if Tomcat could handle
WebSockets, Comet, and "normal" http requests from a single port.

As far as controlling client send queue, I have already requested it over a
year ago: https://issues.apache.org/bugzilla/show_bug.cgi?id=50495. It was
suggested that I propose a patch and the request was closed with "will not fix"
status. I was given some pointers on how it works, but did not think that
patching Tomcat source code is a good long term solution for us. I thought that
now will be a good time to address it for both WebSockets and Tomcat Comet
since the underlying plumbing is getting reworked anyway and may be shared. 
By the way, Grizzly framework actually does have the ability to limit client
send queue with a single API method call.
Thanks

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org