Node.js module 1.0 plans

Events happening in the community are now at Drupal community events on www.drupal.org.
Anonymous's picture
Posted by Anonymous on September 25, 2011 at 4:59am

i'm planning to release node.js module as a 1.0 in the next 4 weeks or so.

soooo, i'm doing some of the 'really should be fixed before 1.0' tasks. this includes:

  • moving a bunch of stupidly-hard-coded url settings from server.js into nodejs.config.js, and documenting them all in nodejs.config.example.js
  • properly prepending a basePath to all http methods so auth will work as expected for non-default urls
  • not allowing server.js to run with a blank serviceKey by default
  • renaming 'backendSettings' to 'settings'
  • getting rid of references to 'Drupal'
  • fixing bugs i've found when making sure the docs match the code and vice-versa
  • allowing server extensions to declare settings, and merging them in when loading the extension
  • allowing server extensions to get access to more events and variables (this whole thing feels ugly, but i think fixing it is post-1.0)
  • actually aggregating messages we enqueue in drupal into one http request to node.js

pulling the latest code will break your install, so make sure you do it a test env first, adjust code, etc.

feel free to ask questions/hurl abuse at me in IRC, and/or open up issues if i've broken anything that adjusting config can't fix.

also - please start shouting now about stuff you want pre-1.0. basically, the next week or so will be the last chance to flag anything so we can get it in.

Categories:

node.js

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

AltStyle によって変換されたページ (->オリジナル) /