incubator-wave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nelson Silva <nelson.si...@gmail.com>
Subject Re:A proposal for the websocket issue
Date Wed, 19 Oct 2011 21:06:39 GMT
Have you tried jetty 7.5.x ? In 7.5.0 they added draft 13 support. It might
be simpler to make socket.io work.
No dia 19 de Out de 2011 17:43, "Vicente J. Ruiz Jurado" <
vjrj@ourproject.org> escreveu:

> Hi again,
>
> I was trying different things with the websocket issue.
>
> Currently I have a WIAB using jetty 8 that seems to work (tested with
> chromium 15), but as socketio-java depends on jetty 7 (and don't support
> the current specification of websocket) I have commented the socket.io
> servlet.
>
> Nowadays we have a conditional "use_socketio = false/true" in the server
> config, to use raw socket or socket.io.
>
> My proposal (I'm not a expert at all on this so please correct me):
> - To remove this conditional server configuration and use both of them
> at the same time. I'm not sure if this is possible.
> - To detect in the client side if websocket is supported natively, if
> so, use /socket/ servlet (jetty 8 websocket support).
> - If not try to use /socket.io/ (but a version patched with the
> websocket transport disabled). So, firefox will use this servlet and
> them other transports.
>
> This solution (if possible) should work with proxies.
>
> It can be a temporal solution while websocket is more widely supported
> and while we evaluate other solutions.
>
> Any comments very appreciated.
>
> Bests,
> --
> Vicente J. Ruiz Jurado
>
> http://comunes.org
> http://ourproject.org
> http://homes.ourproject.org/~vjrj/blog
>
>  "When a white army battles Indians and wins, it is called a great
>  victory, but if they lose it is called a massacre." [Chiksika, Shawnee]
>
>
>
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message