tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 51181] Add support for Web Sockets
Date Fri, 10 Feb 2012 09:45:41 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=51181

--- Comment #33 from Pid <bugzilla@pidster.com> 2012-02-10 09:45:41 UTC ---
(In reply to comment #31)
> Flexibility more than anything, the developer may require access to the request
> in order to determine / set the initial state of the socket or application.

4.2.1.10 says "Optionally, other header fields, such as those used to send
cookies or request authentication to a server." Would just the header map be
enough?

Given that these are potentially long running requests, keeping the original
request object around might not be such a good idea. Would passing in a minimal
or partial object copy be better?

You wouldn't want to be able to permit a write to the ServletOutputStream for
example.

-- 
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


Mime
View raw message