On 4/26/07, Reich, Matthias <[EMAIL PROTECTED]> wrote:
Well, anyway the lifecycle should be well-defined, and I doubt that it
currently is well-defined.
If I try to find a better name for class CometEvent which reflects the
lifecycle of it's instances
according to the current implementation, t
at Users List
> Subject: Re: comet events and connections
>
> > I think that the comet api represents a socket connection.
> The event life
> > cycle is bound to the connection life cycle. You get an END
> (or ERROR etc)
> > when the connection gets closed. But when
>> Exception in thread "Thread-17" java.lang.NullPointerException
>> at
>> org.apache.catalina.connector.CometEventImpl.close(CometEventImpl.java:84)
>> at
>> com.mrtattle.tcniotest.CometServlet$Transport.close(CometServlet.java:42)
>> at com.mrtattle.tcniotest.CometServlet$1.run(Co
Daniel Doubleday wrote:
I don't think that a event.close() call should throw a NPE when the event
is
already closed. But I would rather catch an exception when I am writing
to
response object that has been closed.
that is possible to do, do you have the stack trace of the NP
On 4/25/07, Daniel Doubleday <[EMAIL PROTECTED]> wrote:
Here is the stack trace:
Exception in thread "Thread-17" java.lang.NullPointerException
at
org.apache.catalina.connector.CometEventImpl.close(CometEventImpl.java:84)
at
com.mrtattle.tcniotest.CometServlet$Transport.close(Com
>> I don't think that a event.close() call should throw a NPE when the event
is
>> already closed. But I would rather catch an exception when I am writing
>> to
>> response object that has been closed.
>
> that is possible to do, do you have the stack trace of the NPE?
Here is the stack trace:
Daniel Doubleday wrote:
Hi this post is a follow up from
http://issues.apache.org/bugzilla/show_bug.cgi?id=42198 where this post does
not belong.
I want to find out if my understanding of the comet api in tomcat is right
concerning how connections are handled and event are triggered. I have a
ve
