Your best bet is possibly to write a wrapper for a wakanda/ssjs socket that makes it mimic an asynchronous node.js socket, alternatively, you could do the inverse, but it's a lot harder to do.
Or, you could wrap it in promises, which would provide a potentially more unified interface, but that too is a questionable approach. – Micheil Smith On 28/05/2012, at 1:41 AM, Eric S wrote: > > > On Sunday, May 27, 2012 12:51:54 PM UTC-7, Serti Ayoub wrote: > so, what can be the solution? > > Well, I can see two solutions, the first of which you've already dismissed > (switching to async IO), and the second, I couldn't even begin to estimate > the amount of work needed. That would be to write some C code to do the IO > for you, and then tie that into a module for node. It might be as easy as > returning a file descriptor that's compatible with the fs module and then > using the Sync methods in the fs module to do the IO, but I wouldn't count on > it. It may take having your own code to open, close, read and write the > socket. Be aware that sync IO causes server-wide bottlenecks, which is why > you won't find much sync IO code in node. > > > > > > > -- > 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
