Ah! Ok, you could communicate directly with your Scala program, via net sockets. Instead of writing all the communication stuff, you could try:
https://github.com/substack/dnode There is a Java implementation (see the page) of dnode protocol, I guess you can use it in your Scala app. It can expose some methods to you Node.js application. It manage the request/reply process, via a callback, AFAIK. Angel "Java" Lopez http://ajlopez.wordpress.com http://twitter.com/ajlopez On Thu, Jun 14, 2012 at 5:17 AM, Oren ZBM <[email protected]> wrote: > Hi, the other process, which should indeed be running continuesly, is > Scala. I'm currenlty considering using redis to communicate with the Scala > process. > > I want to pass some text and additional parameters. JSON representation of > a not too complicated object. > > > > Oren > -- > > On Wednesday, June 13, 2012 9:05:14 PM UTC+1, ajlopez wrote: > >> Hmmm... I guess Oren wants to have a process running, not to launch it >> again in each request. >> >> If the process launch in each request is acceptable, then you could try >> https://github.com/**TooTallNate/node-cgi<https://github.com/TooTallNate/node-cgi> >> >> or other options (try: npm search cgi) >> >> It it is not acceptable, then ... hmmmm... FastCGI? I don't know if a >> FastCGI server exists written for Node.js. Related thread >> https://groups.google.com/**group/nodejs/browse_thread/** >> thread/6e852be9ae4e7063/**2c048f624147324c<https://groups.google.com/group/nodejs/browse_thread/thread/6e852be9ae4e7063/2c048f624147324c> >> "It would be great if we could use Node as a webserver to service PHP, >> Perl, Python etc... requests, passthrough the response or process it >> further before returning to client. " >> >> >> If FastCGI is not the way then: >> >> - What kind of information you need to pass to the other process? a >> simple string? >> - The other process is a node.js program? or any other executable? >> >> On Wed, Jun 13, 2012 at 4:38 PM, P. Douglas Reeder >> <[email protected]>wrote: >> >>> As you've described it, you could simply use the child_process module >>> and subscribe to the "exit" event. No need for a queue. >>> >>> -- >>> Job Board: http://jobs.nodejs.org/ >>> Posting guidelines: https://github.com/joyent/**node/wiki/Mailing-List-* >>> *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 >>> nodejs+unsubscribe@**googlegroups.com<nodejs%[email protected]> >>> For more options, visit this group at >>> http://groups.google.com/**group/nodejs?hl=en?hl=en<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 > -- 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
