until the connection closes that everything is secure? (ie. no risk of
XSS for example). If "pure" WebSocket is not supported, do all the
> Yeah, everyone contributing to Socket.IO rock. I built a prototype in under
> a week and got funding already for it. It's only because of Node.js,
> Socket.IO, and a few other libs that this type of accomplishment can happen.
>
> Thanks,
> Francois
>
>
>
>
>
>
>
>
>
> On Mon, Nov 1, 2010 at 7:33 PM, Matt Pardee <
matt.par...@gmail.com> wrote:
> > Fantastic Guillermo, adding installation to the list of ToDos today
> > after I get some other things handled, will report back with any
> > issues if I encounter them. Thank you for your dedication and hard
> > work to this wonderful library, it's indispensable for the project I'm
> > working on (and future projects I'm sure). Cheers~
>
> > On Nov 1, 2:57 pm, Guillermo Rauch <
rau...@gmail.com> wrote:
> > > Forgot to mention some other major improvements:
>
> > > - rememberTransport was fixed
> > > - There's now a connection timeout that allow
socket.io to try
> > multiple
> > > transports per client on the event that one doesn't work (eg: Flash
> > > WebSocket behind corporate proxies)
> > > - Automatic (and lightweight) json encoding. You can now .send({ your:
> > > 'object' })
>
> > > --
> > > Guillermo Rauchhttp://
devthought.com
>
> --