Roadmap #51

3rd-Eden opened this Issue Sep 5, 2013 · 9 comments


None yet

4 participants

Primus member

Primus has grown into a framework we can all depend upon in our daily lives. It is and will always be an innovative way to work and build real-time applications.

Feature & API freeze

The base of Primus is feature complete. Additional logic and features can easily be added on top of Primus through the plugin interface. The only features that might be added in the future would be those that improve the connectivity and stability of Primus or an enhancement of the currently available methods. One of these features might be:

  • Port degrading or upgrading for WebSocket connections.
  • Upgrading and downgrading between transformers using 1 single JS file.

New transformers

Transformers are the most important part about Primus. They are the engines that Primus rides upon. We're currently supporting some of the most popular real-time frameworks:

  • Engine.IO
  • Socket.IO
  • SockJS
  • WebSockets
  • Browserchannel

But there a lot more frameworks and transports available that we're not yet supporting. In the future we should add support for:

With the addition of Flashsockets we should also start supporting them in:

  • Engine.IO
  • Socket.IO

As they've been disabled because of the engineering overhead it takes to get this running smoothly. Currently all real-time systems require you to use your own Node.js powered real-time server. The ultimate goal for this project is to prevent lock-in, this includes lock-in from Node.js. In order to support that we can add support for lightstreamer. They provide a node.js module to interact with their services so in addition to the 2 transformers listed above, we should start with integrating cloud solutions:

Better static support

Serving files from the /primus pathname is really convenient, we should optimize our file serving and make it easier to add files. Which is needed for serving the flash files and additional libraries for the FlashSocket transport.


There is nothing more important in this project then tests. While we have great coverage already, we can still improve this. I've setup a sauselabs account so we can have automated browser testing. We've tried using testling before, but it failed misserably and because it's build on browserify, the stacktraces and the error feedback that you get from it is completely useless. So this needs to addressed

  • Run client tests on saus labs
  • Write more tests for the clients
  • Write even more tests
  • Write integration tests


We've purchased the domain name, we should add a proper website with documentation and API references for the client, spark and server interface as wel as a list of primus modules.

  • Run the application @nodejitsu
  • Design a website
  • Add API reference material
  • Add another working demo of Primus.
Primus member

FYI: This roadmap is open for suggestions, feel free to comment on this post or reference it from other issues.


I think Primus needs a home website. Is that on your roadmap? I do see that you already have the domain


Primus member

@cayasso That is correct, adding it to the roadmap.


And a logo, here is my proposal :)


Primus member

But yea, I do like that font 👍


Yep thats the one I used

@3rd-Eden 3rd-Eden was assigned Sep 6, 2013

Support for simpleio would be great!


Awesome logo :)

While I can't speak for everyone, I do have a hunch that the DocPad Community would be ecstatic to help you with a website for primus if you'd like? Using DocPad, we could display the docs really nicely. Most similar DocPad website would be that for Emmet as well as their documentation site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment