Ok, created an issue for that. https://github.com/kof/simpleio/issues/4
Basically I don't even create a server within simpleio. User need to create a server using any framework and then call simpleio methods and forward the params. I think simpleio interface is lower level and though more flexible than all the the other solutions. Oleg On Monday, July 8, 2013 9:45:24 PM UTC+2, Mikeal Rogers wrote: > > from my limited time in the code this is what i would say: > > You have a slight difference in the implementation of the client and > server API objects, which is the biggest difference from > socket.io/engine.io. The "socket" object in engine.io (which happens to > be enough of a valid Stream to support my use case) is what I would be > looking to replace. If the features you're adding, which are great, were > built as extensions on a unified interface that handles the actual long > polling and delivery of opaque strings I could use that module provided it > implemented the Stream interface. > > Myself and many others have built features on top of engine.io and shoe > by building on top of duplex streams which means that if these were similar > streams that just delivered the strings from one end to the other it would > be a simple change to swap out engine.io/shoe. > > Here are some examples: > > https://github.com/mikeal/eiojson/blob/master/index.js#L29 > https://github.com/mikeal/eioemitter/blob/master/index.js#L5 > https://github.com/mikeal/eiomethods/blob/master/index.js#L19 > > -Mikeal > > On Jul 8, 2013, at 12:36PM, Oleg Slobodskoi > <ole...@googlemail.com<javascript:>> > wrote: > > Please take a look at the code and let me know what you would need to make > it usable for your usecase. > > On Monday, July 8, 2013 9:31:21 PM UTC+2, Mikeal Rogers wrote: >> >> Interesting. >> >> I'm basically using engine.io as a simple stream. I've written several >> modules for the features that I need on top of that stream but I would like >> to see what it looks like if I went and replaced the underlying >> engine.iostream. >> >> Would be cool if the underlying transport was abstracted similarly to >> engine.io, I'd strongly consider switching since I'm equally perplexed >> by a lot of the code in engine.io and I'm only using longpoll. >> >> -Mikeal >> >> On Jul 8, 2013, at 12:19PM, Oleg Slobodskoi <ole...@googlemail.com> >> wrote: >> >> I took lots of time to read engine.io too, I actually wanted to use it. >> >> 1. Its not ready and buggy, lots of things needs to be done >> 2. There is still a bunch of complicated stuff I don't need >> 3. Its just the transport, for scale we need actually everything >> socket.io does too >> >> >> I have tried to fix the new socket.io with engine.io inside but I >> aborted it after some basic design problems in terms of interaction with >> storages. >> >> Am 08.07.2013 um 18:11 schrieb Mikeal Rogers <mikeal...@gmail.com>: >> >> I too had issues with socket.io but have found engine.io to be quite >> pleasant. Did you try engine.io and come to similar frustrations? >> >> On Jul 8, 2013, at 6:01AM, Oleg Slobodskoi <ole...@googlemail.com> wrote: >> >> Hello there :) >> >> I have recently started a new project after lots of frustration with >> socketio. Simpleio is not a full replacement of all the features of >> socketio, but its actually everything one might need to create chatty like >> messaging on any hosting using a long polling which works everywhere. Most >> important design goals are: >> >> - support for router/balancer without sticky sessions (f.e. Heroku) >> - optimized for horizontal scaling >> - reliable message delivery (built-in delivery confirmation) >> - multiplexing on the server and client >> - lightweight client (appr. 2.5 kb minified and gzipped) >> - simple client spec, which can be implemented easily in any language >> >> Native clients for anroid and ios are will be usable in some weeks. >> >> Best, >> Oleg >> >> http://github.com/kof/simpleio >> >> >> >> -- >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to nod...@googlegroups.com >> To unsubscribe from this group, send email to >> nodejs+un...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "nodejs" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to nodejs+un...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> >> >> -- >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to nod...@googlegroups.com >> To unsubscribe from this group, send email to >> nodejs+un...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "nodejs" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to nodejs+un...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> >> >> -- >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to nod...@googlegroups.com >> To unsubscribe from this group, send email to >> nodejs+un...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "nodejs" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to nodejs+un...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> >> > -- > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to nod...@googlegroups.com <javascript:> > To unsubscribe from this group, send email to > nodejs+un...@googlegroups.com <javascript:> > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to nodejs+un...@googlegroups.com <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
