Hi! Do we have best practices on this use-case, like cloudup maybe? A simple use case like, file downloader desktop app (since we have `request` module on npm) can be implemented like, for example, having UI written in QtWebKit and call node process to download file is a viable approach? Or we can embed node so we only have one process, since we can embed libuv?
Thanks Dhi On Tuesday, March 16, 2010 12:47:16 PM UTC+7, Andrey Tarantsov wrote: > > > > I want to embed a node.js-based server inside my application — > > > preferably something running on a separate thread. Looking at main.cc > > > and main.js, I can't spot anything that would block this approach. > > > > What is your application? I think in most cases running node as a > > subprocess would be best. > > I think initially I'll go with a subprocess indeed. I'm writing an OS > X desktop app, and my concern is that the user might be confused to > see several processes for an app (say, in Activity Monitor). > > Another reason to embed node.js is to try to port some bindings like > JSCocoa to work with it. (Of course, this, too, may and probably > should be architectured in another way.) > > Basically, I just wanted to know that embedding is an option if I > happen to need it in the future. > > -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
