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 50495] Comet connector needs ability to access the client send queue.
Date Tue, 04 Jan 2011 14:42:21 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=50495

Mark Thomas <markt@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX
           Severity|blocker                     |enhancement

--- Comment #1 from Mark Thomas <markt@apache.org> 2011-01-04 09:42:15 EST ---
This is an enhancement request, not a blocker.

This enhancement looks like something that is application specific. There are
various reasons why a generic solution would be difficult:
- the Comet API (and all of Tomcat's internals) has no concept of a message
- bytes written to clients are buffered are various points both under Tomcat's
control and completely outside of Tomcat's control
- the criteria for compressing messages is something that would be very hard to
make generic

With all this in mind, I am resolving this as WONTFIX.

That said, if there are changes to the Comet API you would like to propose (in
the form of a patch) that would make an application level implementation of
these features easier, feel free to re-open this issue and attach your proposed
patch.

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