Hi, I played around a bit with the wschat example in chrome 14. Works very well. I came across a small issue when connecting a second client, which I tracked down. patch here: https://gist.github.com/1144267 One small question about the websocket handling in chat.py. Right now, it uses 3 functions (wsChallenge,wsframe,wsdeframe) to handle websocket specifics. Will this remain the handler's responsibility in the future (become part of the handler libraries for all languages)? Or are there plans to have mongrel2 take over these tasks? Thanks, Mathijs
On Sat, Aug 13, 2011 at 11:41:49PM +0200, Mathijs Kwik wrote: > Hi, > > I played around a bit with the wschat example in chrome 14. > Works very well. > I came across a small issue when connecting a second client, which I > tracked down. > patch here: https://gist.github.com/1144267 Fixed, and pushed to develop. > One small question about the websocket handling in chat.py. > Right now, it uses 3 functions (wsChallenge,wsframe,wsdeframe) to > handle websocket specifics. > > Will this remain the handler's responsibility in the future (become > part of the handler libraries for all languages)? > Or are there plans to have mongrel2 take over these tasks? Not sure right now. In theory this can go into Mongrel2, but I wanted to avoid it while they play around with the spec and then when it's finalized move it in. It's way easier to change it in the Python code example than to do it in Mongrel2. -- Zed A. Shaw http://zedshaw.com/
On Sun, Aug 14, 2011 at 9:15 PM, Zed A. Shaw <zedshaw@zedshaw.com> wrote: > On Sat, Aug 13, 2011 at 11:41:49PM +0200, Mathijs Kwik wrote: >> Hi, >> >> I played around a bit with the wschat example in chrome 14. >> Works very well. >> I came across a small issue when connecting a second client, which I >> tracked down. >> patch here: https://gist.github.com/1144267 > > Fixed, and pushed to develop. > >> One small question about the websocket handling in chat.py. >> Right now, it uses 3 functions (wsChallenge,wsframe,wsdeframe) to >> handle websocket specifics. >> >> Will this remain the handler's responsibility in the future (become >> part of the handler libraries for all languages)? >> Or are there plans to have mongrel2 take over these tasks? > > Not sure right now. In theory this can go into Mongrel2, but I wanted > to avoid it while they play around with the spec and then when it's > finalized move it in. It's way easier to change it in the Python code > example than to do it in Mongrel2. True, But it will take time for other handlers to get it too. It's not that much code though, so I can probably port it myself. But I haven't done any bit-juggling in javascript before :) > > -- > Zed A. Shaw > http://zedshaw.com/ >