You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Matthias Wessendorf <ma...@apache.org> on 2009/01/19 23:50:37 UTC
[comet] state of the implementation
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 some thoughts of a more common module for this? Like working
on the API
with Jetty/dojo and just *reuse* the API, here in Tomcat and just care
about the actual
IMPL ?
Thanks,
Matthias
[1] http://svn.apache.org/viewvc/tomcat/trunk/modules/bayeux/java/org/apache/
(and subfolders)
[2] http://svn.cometd.com/trunk/cometd-java/api/src/main/java/org/cometd/
[3] The package dojox.cometd was renamed to org.cometd -->
http://cometdproject.dojotoolkit.org/documentation/cometd-java
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [comet] state of the implementation
Posted by Flo <fl...@gmx.de>.
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-unsubscribe@tomcat.apache.org
> >> For additional commands, e-mail: dev-help@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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [comet] state of the implementation
Posted by Matthias Wessendorf <ma...@apache.org>.
> 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-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: dev-help@tomcat.apache.org
>>
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [comet] state of the implementation
Posted by Matthias Wessendorf <ma...@apache.org>.
On Mon, Jan 19, 2009 at 3:36 PM, Remy Maucherat <re...@apache.org> 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.cometd" (-> [3]).
>>
>> Another question is, is the tomcat module up-to-date? Since I see some diffs on
>> the classes etc? (-> API)
>>
>> Are there some thoughts of a more common module for this? Like working
>> on the API
>> with Jetty/dojo and just *reuse* the API, here in Tomcat and just care
>> about the actual
>> IMPL ?
>
> This has been discussed one month ago. To summarize, this stuff is not a
> standard, so something in the org.apache namespace was used.
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
-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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [comet] state of the implementation
Posted by Remy Maucherat <re...@apache.org>.
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 up-to-date? Since I see some diffs on
> the classes etc? (-> API)
>
> Are there some thoughts of a more common module for this? Like working
> on the API
> with Jetty/dojo and just *reuse* the API, here in Tomcat and just care
> about the actual
> IMPL ?
This has been discussed one month ago. To summarize, this stuff is not a
standard, so something in the org.apache namespace was used.
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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org