Ringobot log - RingoJS IRC channel: #ringojs on irc.freenode.net

2010-09-04:

[12:44] <robi42> hi, while playing a bit with `ringo/webapp/websocket` i figured it would be nice to also have the respective outbound socket connection exposed, see: http://gist.github.com/565192
[12:46] <robi42> this way the chat example from http://blogs.webtide.com/gregw/entry/jetty_websocket_server works nicely (tested with chrome + ff 4 beta, btw)
[14:34] <oberhamsi> how is it different from using WebSocket.send directly? or is the chat doing other stuff too to the outbound socket?
[14:35] <oberhamsi> btw i'm successfully using this for websockets fallback in FF3 http://github.com/gimite/web-socket-js
[14:36] <robi42> re: fallback cool
[14:37] <robi42> re: chat example they store connections in an array
[14:37] <oberhamsi> yep.. cool that it works. and the API stays the same even if it does flash.. just do new WebSocket() and the right thing happens
[14:37] <robi42> http://dav.robert42.com/websocket-chat.zip for checking it out conveniently :)
[14:38] <oberhamsi> will check it out.
[14:38] <robi42> storing connections is for handling members in chat room, so to speak
[14:38] <oberhamsi> i'm storing the socket objects as passed to connect callback in array
[14:39] <oberhamsi> i get it :) not sure yet why it's better to only store outbound socket
[14:39] <oberhamsi> this fallback is nice.. if window.WebSocket is not defined it creates it as wrapper around flash with same API
[14:40] <robi42> sweet
[14:42] <robi42> btw, i guess storing sockets would work for that chat example as well
[14:47] <oberhamsi> cool stuff
[14:47] <robi42> :)
[14:48] <oberhamsi> re: port of http://github.com/LearnBoost/Socket.IO-node
[14:48] <robi42> and it works w/o outbound stuff as you said, replaced zip on dav
[14:49] <oberhamsi> didn't dig too deep, but isn't socket.io-node mostly about providing fallbacks with same interface on server?
[14:49] <oberhamsi> like XHR polling / streaming
[14:49] <robi42> had a first look into the lib
[14:49] <robi42> and yep
[14:49] <robi42> they basically define different transports
[14:49] <robi42> to fallback to
[14:50] <robi42> wrapping websocket api
[14:50] <oberhamsi> okay i thought so. well with flash fallback i don't care much for that.
[14:50] <robi42> :)
[14:51] <oberhamsi> what i would like, though, is easier way to serve the stupid XML security policy file on port <i forgot>. socket.io-node seems to do that
[14:51] <oberhamsi> (for flash)
[14:52] <robi42> yep, that would be nice. didn't dig into that yet, tho
[14:54] * robi42 afk
[18:21] <robi42> fyi: for the fun of it (temporarily) put that little websocket chat demo thing on http://log.robert42.com/ :)
[22:59] <keeto> hey guys! is there a function or property that'll return the current version?
[23:11] <earl> >> require('ringo/engine').version
[23:11] <earl> [0, 6]