Hi, I had the same concern (and offered to have a look at the current Tomcat implementation and eventually contribute an impl for the current API). The gap actually turned out to be larger than expected, so it will depend on our project plan during the next weeks, whether we'll stick with Tomcat (and provide that impl) or move to Jetty. That discussion is still open in our project team, so no decision yet :-(
Regards, Flo Am Dienstag 20 Januar 2009 schrieb Matthias Wessendorf: > > oh, I see. Thanks > > > > So, I think I have one more question, on the completeness. What are the > > current plan? "Only" all the MUST/SHALL NOTs ? Or also optional, > > e.g streaming (as transport), to just name one > > found the thread. > Thanks > > > -Matthias > > > >> BTW, this Tomcat cometd API is also available in JBoss AS 5, so that > >> should mean good production deployment availability (eventually). > >> > >> Rémy > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > >> For additional commands, e-mail: dev-h...@tomcat.apache.org > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > twitter: http://twitter.com/mwessendorf --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
