Re: Another Comet 6.0.10 question

2007-04-04 Thread Rémy Maucherat
On 4/4/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote: Hmm... I don't work under Windows, I use Ubuntu Linux, but I'll try figure out why it keeps sending me READ events after the end of stream was reached; I'll get back to you on that one (I'll see if I can make a small test program which exhi

Re: Another Comet 6.0.10 question

2007-04-04 Thread Sebastiaan van Erk
Hi, thanks very much for the replies. Rémy Maucherat wrote: On 4/4/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote: Ok, so I get a -1 on a read. Now what do I do? If I just return from the event handler I immediately get another read :-(. If I close the event I can't do output anymore. Sinc

Re: Another Comet 6.0.10 question

2007-04-04 Thread Rémy Maucherat
On 4/4/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote: Ok, so I get a -1 on a read. Now what do I do? If I just return from the event handler I immediately get another read :-(. If I close the event I can't do output anymore. Since there's not going to be any additional data from the client,

Re: Another Comet 6.0.10 question

2007-04-04 Thread Sebastiaan van Erk
Ok, so I get a -1 on a read. Now what do I do? If I just return from the event handler I immediately get another read :-(. If I close the event I can't do output anymore. Can't it just send me ERROR/TIMEOUT events, just like what would happen if no READS arrive at all? In that case I can do a

Re: Another Comet 6.0.10 question

2007-04-04 Thread Rémy Maucherat
On 4/4/07, Rémy Maucherat <[EMAIL PROTECTED]> wrote: Ok, that javadoc is a little bit out of date (ex: returning false). However, it is still valid: if you get a read event, you're supposed to do at least one read, and it could return -1 (if it got that from the client). If it fails to read data

Re: Another Comet 6.0.10 question

2007-04-04 Thread Rémy Maucherat
On 4/4/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote: 2) I keep getting READ events after reading all data from the stream (EOF reached). Now I don't want to close the event because I still want to write stuff, but I can't just return from the read event because I'll get another, causing a bus

Re: Another Comet 6.0.10 question

2007-04-04 Thread Rémy Maucherat
On 4/4/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote: Hi, The pages on Comet say the following about the read event: EventType.READ: This indicates that input data is available, and that one read can be made without blocking. The available and ready methods of the InputStream or Reader may b

Re: Another Comet 6.0.10 question

2007-04-04 Thread Sebastiaan van Erk
I have been reading the EventType.READ explanation over and over again, and now I have even more questions. 1) It says I should return false or throw an IOException when I get EOF. However, the event method has a void return type, so I don't know how to do the first. And if it's not unexpected

Another Comet 6.0.10 question

2007-04-04 Thread Sebastiaan van Erk
Hi, The pages on Comet say the following about the read event: EventType.READ: This indicates that input data is available, and that one read can be made without blocking. The available and ready methods of the InputStream or Reader may be used to determine if there is a risk of blocking: the