> > Could you indulge me and try the client with the sleep? > > > just did, worked exactly as before. > event: BEGIN, subtype: null > event: READ, subtype: null > Read 10 bytes: comet test for session: A01334D0AC22505DCD4B323820963FEC > read error > event: ERROR, subtype: TIMEOUT
Hmm, not sure where to go from here then. Here's my output: Jan 29, 2008 4:36:23 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 1173 ms event: BEGIN, subtype: null event: READ, subtype: null Read 10 bytes: comet test for session: CAF116EB9DF8BB1C5DD3170FC70F2394 event: END, subtype: null > If you are unsure if you have messed up Tomcat binaries, then I would test > this one > http://people.apache.org/~fhanik/tomcat/tomcat-5.5/v5.5.26/bin/ I don't think it's bad binaries 'cause I've rebuilt a number of times, but I'm happy to give new binaries a try. You're pointing to tomcat 5.5 binaries though -- I thought comet was a 6.0 feature. Should I try the 5.5 binaries anyway? > yes, we are very aware that the sample code is not the best for getting > started, we are looking to replace it, but it takes time and resources. I didn't mean to be critical -- merely pointing out an area of confusion for me. In fact, I thought the sample code was reasonably sufficient for me to get up and running. My main issues were getting the client http chunking working properly. > contributions always welcome! I'm pretty sure you don't want me writing the sample code! :) I'm still learning here, but I hope that our dialog is a contribution of sorts. As I mentioned before, my comet app is working fine using non-chunked httpurlconnections. This end event issue is not a roadblock for me -- I'm pursuing it to help tomcat and tomcat users, and satisfy my own curiosity of course. :) Hopefully others will learn from my misunderstandings, code snippets, etc. Peter --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
