Arnout Kazemier

^ and that shouldn't be to hard to build. It might even make sense to just build that in to primus directly.

@maxguzenski Sure, localStorage is slow, but it might be worth the extra overhead instead of forcing your users to open multiple connections in each tab and quadruple their bandwidth. If...

@jgrund I haven't done any testing yet, as this is mostly a nice to have feature and nothing something super critical.

Primus wise this should be possible after merging our browserify branch as it will remove DOM references from our code (used for url parsing atm)

@rvagg Yes, writing lessons should be relatively straight forward task. I'll take a look at issue rvagg/workshopper#12 but I can't really provide useful feedback until I've actually started writing lessons...

@STRML The pipe method should and will only be added when require the generated client with browserify as we will try to inherit from stream module instead of the EventEmitter.

Hey, I don't know how feasable it is to implement this in to primus. We already ran in some issues with integrating Faye in to primus (which follows the bayeux...

Aye that's a really good find, and solid steps to reproduce!

@gcmartijn but why are sending `primus::` prefixed messages?

@sailxjx Fixed? There is nothing fix here. Just implement the required heartbeats and be done with it.