2011/10/1 Konstantin Kolinko :
> Hi!
>
> I was reading the Comet API documentation, that is "aio.html" in the
> docs and Javadoc of catalina.comet.* classes.
>
> Here are several notes.
>
Answering several of my notes below.
>
> CometEvent.java:
> ===
Hi!
I was reading the Comet API documentation, that is "aio.html" in the
docs and Javadoc of catalina.comet.* classes.
Here are several notes.
CometEvent.java:
===
- #setTimeout():
a) @param timeout says it is positive value.
With recent Mark's fixes to timeout h
On 30/04/2010 07:51, Konstantin Kolinko wrote:
> There is a difference in Comet API that will require all TC6 Comet
> applications
> to be patched and recompiled before deploying them to TC7:
>
> Comet classes were moved from "org.apache.catalina" to
> "org.apa
Would it be possible to just create an optional package that has all the
old class names and their implementation is just an extends of the new
version? (As well as being marked deprecated)
-Tim
On 4/30/2010 2:51 AM, Konstantin Kolinko wrote:
There is a difference in Comet API that will
On 04/30/2010 08:51 AM, Konstantin Kolinko wrote:
> There is a difference in Comet API that will require all TC6 Comet
> applications
> to be patched and recompiled before deploying them to TC7:
>
> Comet classes were moved from "org.apache.catalina" to
> "org.
There is a difference in Comet API that will require all TC6 Comet applications
to be patched and recompiled before deploying them to TC7:
Comet classes were moved from "org.apache.catalina" to
"org.apache.catalina.comet".
What do you think, is this change acceptable for
Peter Rossbach wrote:
Yes, I want implement access filter. As filter detect overload, it set
a event retry timeout and give back the event.
Later the event comes back and mark as event type RETRY.
I think you have two solutions:
- do stuff to get notifications that some pool connection is av
HI Remy
Am 15.04.2007 um 13:53 schrieb Remy Maucherat:
Peter Rossbach wrote:
Hi Filip and Remy
Often, if my HTTP request needs to get a database connection and
the connection pool is empty,
the request will block for some period of time. The problem is
that the blocking request will consum
Peter Rossbach wrote:
Hi Filip and Remy
Often, if my HTTP request needs to get a database connection and the
connection pool is empty,
the request will block for some period of time. The problem is that the
blocking request will consume a thread while it it blocking.
How can I free up the re
Hi Filip and Remy
Often, if my HTTP request needs to get a database connection and the
connection pool is empty,
the request will block for some period of time. The problem is that
the blocking request will consume a thread while it it blocking.
How can I free up the request thread when the
e good job...
Christophe
-Message d'origine-
De : Remy Maucherat [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 24 janvier 2007 14:48
À : Tomcat Developers List
Objet : Re: Comet API and InputStream.available()
Christophe Pierret wrote:
Here is what I understood:
Assumption #1: ==
EMAIL PROTECTED]
Envoyé : mercredi 24 janvier 2007 14:48
À : Tomcat Developers List
Objet : Re: Comet API and InputStream.available()
Christophe Pierret wrote:
> Here is what I understood:
>
> Assumption #1: When you receive a
> CometEvent.EventType.READ event, you can
Christophe Pierret wrote:
Here is what I understood:
Assumption #1: When you receive a
CometEvent.EventType.READ event, you can always read() at least one
byte from the request's InputStream without blocking.
Is this correct ? If not correct, then this mail goes directly to
tra
va/io/InputStream.html
for InputStream.available() method contract with the caller.
Note that available() returning 0 makes sense also. In this context, it means
"I cannot guarantee that you can read without blocking".
But returning 0 will force the Comet API user to use the kind of ha
e read (or skipped over) from this
input stream without blocking by the next caller of a method for this input
stream.
When first read occurs, it should then return the real available bytes.
I had to implement this behaviour myself when using Comet API in my product, since I already had a working
n the real available bytes.
I had to implement this behaviour myself when using Comet API in my product,
since I already had a working implementation for a fragmented packet reader
based on ByteBuffer (done for NIO kind of IO).
In this case available() would return byteBuffer.
Christophe Pierret wrote:
I only had to port the patches for
http://issues.apache.org/bugzilla/show_bug.cgi?id=40960
and
http://issues.apache.org/bugzilla/show_bug.cgi?id=37869
These two patches have been merged in HEAD.
Feedback on the Comet API:
- There may be some ways to improve the
There is now a "standart" way to break the "one thread per connection"
limit, due to the current servlet specification, in tomcat.
It took me less than 2 days (and 2 nights ;-) to update my product to
make use of the Comet API (using 6.0.7 beta) while retaining previous
behavio
18 matches
Mail list logo
