00:17:25  * lluadquit (Quit: lluad)
00:42:43  * colinsullivanjoined
03:25:53  * colinsullivanquit (Ping timeout: 248 seconds)
03:30:50  * dennismartenssonjoined
03:31:11  * dennismartenssonquit (Remote host closed the connection)
03:46:12  * colinsullivanjoined
04:01:20  * jakljoined
08:20:24  * mdedetrichquit (Quit: Computer has gone to sleep.)
08:22:40  * colinsullivanquit (Quit: Leaving.)
09:25:08  * vguerrajoined
09:42:08  * dennismartenssonjoined
10:14:14  * dennismartenssonquit (Remote host closed the connection)
10:59:13  * oaljoined
14:26:18  * pierrooojoined
14:56:47  * erobitjoined
15:03:38  * Golesjoined
15:09:17  <erobit>hey folks, looking forward to helping out with ss in any way possible. I've tried many of the *frameworks* out recently and keep falling back to ss due to its minimalist approach
15:10:44  <erobit>owenb_: takes cajones to re-invent until you are sure you have the write core that fits with your core vision of what ss should be. kudos.
15:11:23  <erobit>owenb_: write/right
15:23:20  * Golesquit (Quit: Out.)
15:31:38  * vguerraquit (Remote host closed the connection)
15:37:05  * vguerrajoined
16:44:25  * vguerraquit (Remote host closed the connection)
17:07:19  * lluadjoined
17:08:20  * Golesjoined
17:27:00  * Golesquit (Quit: Out.)
18:24:27  * vtalijoined
18:37:08  * vtaliquit (Ping timeout: 245 seconds)
18:37:55  * erobitquit (Quit: Page closed)
19:42:24  * dennismartenssonjoined
19:53:15  * malditogeekjoined
20:00:44  <malditogeek>guys, what's the api for ws connection callbacks on the server side?
20:17:10  * malditogeekquit (Quit: Leaving.)
20:27:03  * malditogeekjoined
21:04:33  * colinsullivanjoined
21:18:17  * malditogeekquit (Quit: Leaving.)
22:07:51  * malditogeekjoined
23:09:39  * paulbjensenjoined
23:10:41  <paulbjensen>@malditogeek - hi, when you say ws connection, could you explain what you mean?
23:13:03  <paulbjensen>do you mean like socket.io's socket.on 'connection' event binding?
23:13:13  * Golesjoined
23:13:59  * Golesquit (Max SendQ exceeded)
23:14:44  * Golesjoined
23:20:00  <malditogeek>paulbjensen: hi Paul, yeah, exactly that
23:20:53  <paulbjensen>what ws transport library are you using? default, engine.io, sockjs
23:21:52  <malditogeek>paulbjensen: client-side you have ss.server (https://github.com/socketstream/socketstream/blob/master/new_project/client/code/app/entry.coffee#L6) was wondering where can I listen to those events server-side
23:21:54  <malditogeek>paulbjensen: default
23:22:06  <paulbjensen>also, are you using socketstream 0.3.2 or master branch?
23:22:39  <malditogeek>0.3.2
23:24:42  <paulbjensen>ok, I'll have a bash at getting to it
23:32:14  <malditogeek>did the codebase diverged a lot between head and 0.3.2?
23:32:40  <paulbjensen>there was an update: the default is now engine.io
23:41:40  <paulbjensen>I've tried getting access to it, but unfortunately there isn't a public API exposed to it.
23:42:34  <paulbjensen>but it is being used internally: https://github.com/socketstream/socketstream/blob/master/src/websocket/transports/engineio/index.js#L96
23:46:34  <paulbjensen>the best thing I can recommend is forking a copy of SS, and tinkering with the src/websocket/transport file to make it expose the library to the api. Alternatively, open an issue on github, and someone will get to it.
23:48:02  <paulbjensen>Sorry I couldn't fix it (yet). I will be off, good luck and let me know if you manage to resolve it or whether you need someone to fix the issue on github. twitter @paulbjensen.
23:48:07  <paulbjensen>Night
23:48:15  * paulbjensenquit (Quit: paulbjensen)