2 ms·
Trying not to offensive. Two years ago I would find this useful. But I'm so glad I learned Node.js where this can be accomplished with high level sockjs module
by z3t4 12y ago
Trying not to offensive. Two years ago I would find this useful. But I'm so glad I learned Node.js where this can be accomplished with high level sockjs module and nginx in less then five minutes.
https://github.com/sockjs https://github.com/sockjs
- jkarneges 12y agoNo worries! Pushpin isn't really about providing the easiest answer. It's about radically changing how we architect and operate realtime web services. In fact, Pushpin and Node are complementary, and Pushpin has a Node library. If you're already using a language/framework capable of WebSockets or long-lived HTTP connections like Node (or Tornado, or Go, or countless others) then Pushpin's value may not be immediately apparent. It just seems like yet-another-realtime-server thing, right? The long answer is that Pushpin restores the division between API designer, engineer, and operations that we all enjoy in the RESTful API world but that is currently non-existent in the realtime world. But, until you have many servers, a multi-tiered architecture, and a team, this may be hard to appreciate. ;)