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 Tomca
> 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 av
On Mon, Jan 19, 2009 at 3:36 PM, Remy Maucherat wrote:
> On Mon, 2009-01-19 at 14:50 -0800, Matthias Wessendorf wrote:
>> hi,
>>
>> looking at the tomcat comet module [1] and comparing it to the one in
>> jetty/dojo [2],
>> I wonder if the package (api-part) in tomcat shouldn't be named
>> "org.co
On Mon, 2009-01-19 at 14:50 -0800, Matthias Wessendorf wrote:
> hi,
>
> looking at the tomcat comet module [1] and comparing it to the one in
> jetty/dojo [2],
> I wonder if the package (api-part) in tomcat shouldn't be named
> "org.cometd" (-> [3]).
>
> Another question is, is the tomcat module
hi,
looking at the tomcat comet module [1] and comparing it to the one in
jetty/dojo [2],
I wonder if the package (api-part) in tomcat shouldn't be named
"org.cometd" (-> [3]).
Another question is, is the tomcat module up-to-date? Since I see some diffs on
the classes etc? (-> API)
Are there som
