That's kind of what commonjs was. All the sync server side js implementations were there.
Is it still active? Are you specifically wanting "blocking js that is not commonjs"? Saying "nodejs-sync" is a little silly since synchronous APIs would be entirely incompatible with the rest of node. Would be better to create a new name, new flag to fly under, if you want such a fork to gain momentum. -Mikeal On Apr 7, 2012, at April 7, 20121:02 PM, Oleg Podsechin wrote: > But a sync-flavor io libs could nurture another set of projects. Let the > community decide. > > I think it's clear that sync I/O won't be going into Node core. That being > said, I agree that a set of standard sync I/O APIs would be very useful > indeed. It would help unify the currently fragmented efforts and allow for > innovation higher up the stack. > > Would there be interest from others in setting up a separate group, say > "nodejs-sync", where discussion about such a set of APIs could take place? > > The added benefit would be that any posts on the topic of sync I/O could be > redirected there, keeping this group's signal to noise ratio high. > > Oleg > > -- > 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 [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
