Hi,
On Tue, May 7, 2013 at 11:54 AM, Christian <
chriz...@gmail.com> wrote:
> Hi,
>
> let's say, I want to deploy a webapp using cometD, but I need to run it on
> tomcat (7). Right now, what do I have to expect?
> Can I run my cometD app with tomcat? As I've read, cometD uses some special
> type of WebsocketTransportProtocol which only works for Jetty.
Correct.
> So does this mean, my app would work like it would on jetty, the only thing
> I can't use is websockets? What about OOrt?
Oort works the same way: if websocket is available, it uses it,
otherwise falls back to http.
> I guess this is an important question because in big companys like our's I
> can't decide: Hey, let's try Jetty where all the other App Server are
> Tomcat's..
It's not CometD fault if your company has decided to stick to Tomcat, sorry.
CometD is open source, and while everyone is asking for a WebSocket
Tomcat transport, nobody has contributed it.
We have limited resources and we can't do this.
CometD 3 will implement a transport based on JSR 356.
When Jetty9 will have support for 356 (it's on the workings), CometD 3
will have a portable WebSocket transport.
When Tomcat will have support for 356, I don't know. Good luck though.
Again, we're open to contributions.
Michele just got his pull request merged to integrate Jackson 2 (see
https://github.com/cometd/cometd/pull/16).
Florian submitted a pull request that was inspirational to improve
error reporting in 2.6.0.
Just to mention the 2 most recent.
--
Simone Bordet
----
http://cometd.org
http://webtide.com
http://intalio.com
Developer advice, training, services and support
from the Jetty & CometD experts.
Intalio, the modern way to build business applications.