You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Konstantin Kolinko <kn...@gmail.com> on 2010/04/30 08:51:15 UTC
Comet API incompatibility between TC 6 and TC 7
There is a difference in Comet API that will require all TC6 Comet applications
to be patched and recompiled before deploying them to TC7:
Comet classes were moved from "org.apache.catalina" to
"org.apache.catalina.comet".
What do you think, is this change acceptable for us?
IIRC, the cause behind this is
https://issues.apache.org/bugzilla/show_bug.cgi?id=48218
-- to have access to Comet classes when running with a SecurityManager one has
to grant access to "org.apache.catalina" package, which exposes the server API.
If we go on with this, a notice has to be added to
http://tomcat.apache.org/migration.html
I, personally, think that it would be better to move the classes to
their old place.
I think that Servlet 3.0 applications would prefer Servlet Async API,
and if someone uses Comet, access to "org.apache.catalina" can be granted
to those web applications explicitly.
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Comet API incompatibility between TC 6 and TC 7
Posted by jean-frederic clere <jf...@gmail.com>.
On 04/30/2010 08:51 AM, Konstantin Kolinko wrote:
> There is a difference in Comet API that will require all TC6 Comet applications
> to be patched and recompiled before deploying them to TC7:
>
> Comet classes were moved from "org.apache.catalina" to
> "org.apache.catalina.comet".
>
> What do you think, is this change acceptable for us?
Well I would say yes Comet is experimental and each web server has its
own implementation... May be time to think of JSR for comet?
>
> IIRC, the cause behind this is
> https://issues.apache.org/bugzilla/show_bug.cgi?id=48218
> -- to have access to Comet classes when running with a SecurityManager one has
> to grant access to "org.apache.catalina" package, which exposes the server API.
>
> If we go on with this, a notice has to be added to
> http://tomcat.apache.org/migration.html
>
>
> I, personally, think that it would be better to move the classes to
> their old place.
>
> I think that Servlet 3.0 applications would prefer Servlet Async API,
The Async stuff doesn't cover all the stuff Comet could do. But it makes
sense to push customer to use the Servlet 3.0 when that is possible.
Cheers
Jean-Frederic
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Comet API incompatibility between TC 6 and TC 7
Posted by Mark Thomas <ma...@apache.org>.
On 30/04/2010 07:51, Konstantin Kolinko wrote:
> There is a difference in Comet API that will require all TC6 Comet applications
> to be patched and recompiled before deploying them to TC7:
>
> Comet classes were moved from "org.apache.catalina" to
> "org.apache.catalina.comet".
>
> What do you think, is this change acceptable for us?
Yes.
> IIRC, the cause behind this is
> https://issues.apache.org/bugzilla/show_bug.cgi?id=48218
> -- to have access to Comet classes when running with a SecurityManager one has
> to grant access to "org.apache.catalina" package, which exposes the server API.
>
> If we go on with this, a notice has to be added to
> http://tomcat.apache.org/migration.html
Agreed.
> I, personally, think that it would be better to move the classes to
> their old place.
I disagree. Lots of APIs are changing in Tomcat 7, this is just one more.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Comet API incompatibility between TC 6 and TC 7
Posted by Tim Funk <fu...@apache.org>.
Would it be possible to just create an optional package that has all the
old class names and their implementation is just an extends of the new
version? (As well as being marked deprecated)
-Tim
On 4/30/2010 2:51 AM, Konstantin Kolinko wrote:
> There is a difference in Comet API that will require all TC6 Comet applications
> to be patched and recompiled before deploying them to TC7:
>
> Comet classes were moved from "org.apache.catalina" to
> "org.apache.catalina.comet".
>
> What do you think, is this change acceptable for us?
>
> IIRC, the cause behind this is
> https://issues.apache.org/bugzilla/show_bug.cgi?id=48218
> -- to have access to Comet classes when running with a SecurityManager one has
> to grant access to "org.apache.catalina" package, which exposes the server API.
>
> If we go on with this, a notice has to be added to
> http://tomcat.apache.org/migration.html
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org