node package manager
Share your code. npm Orgs help your team discover, share, and reuse code. Create a free org ยป


Why Serialize?

In some cases, (for example adding users to linux box) if you try to run your functions in parallel it will fail.

You want to have very simple queue, that will register each incoming function, and execute it one by one.

For example:

  serializer = require "serializer"
  # here is an example function that will callback after 1 second.
  exampleFunction = (x,callback)-> setTimeout (()-> callback "Finished in 1 sec...with #{x} #{y} #{}"),1000
  # if you run the for loop below, they will approximately all finish at the same time
  for i in [0..10] 
    exampleFunction i,(r)->
     console.log r
  # now you can serialize this function, and it will finish in 10 seconds, running one after another
  serializedExampleFunction = serializer exampleFunction

  # once you get your serialized version of your function, you use it just like you use the original.

  for i in [10..10]
    serializedExampleFunction i,(r)->
     console.log r


$ npm install serializer

To do

- Queue can be persisted to a db (right now, pending functions will die if node process dies)
- Functions that don't have a callback can be serialized (however, i don't know why those need to be serialized)