[nodejs] Best way to send data between php and Node
What's the best technique for sending small amounts of data back and forth between node and php on the same server? Is dNode the best solution for this? Or should I be looking at alternatives else? Thank you! -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: Best way to send data between php and Node
Hi Folks, My intent is not to start a religious debate. Truly. I'm working with a legacy system in php. Rewriting it from the ground up is not an option at the moment. I have a flash client that currently gets commands from php by polling the php server every 10 seconds. (a truly horrible and non-scalable solution I inherited). My goal is to use node as a messaging layer to send commands from php to the flash client over a socket. Flash then would acknowledge receipt of a command and act upon it. In our current world, commands are initiated in php. I'm looking for a good way to set up bi-directional communication between node and php. From php, I'd need to pass in an ip address and a command. Node would then find the client with that ip address and send the command to it. Once I have this up and running I may be able to convince my cohorts to begin building more server code in node. Thanks for your help, Steven -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: Writing to closed connection = Boom!
I missed the 'writable' property. That's a big help. Thanks very much for your help! What about listening for the 'error' event and/or checking if the 'writable' property of the socket is set to false? -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Writing to closed connection = Boom!
What's the best way to deal with closed socket connections? I have a simple node.js socket server, and a client in Flash. If I refresh my web browser, the node.js socket server gets an 'end' event, Node knows the connection is closed. All is well. However, if the network were to have a problem (for instance someone unplugs and replugs an ethernet cable on the client computer). The socket connection is broken, but the server does not get an 'end' 'close' or other event that I can see. Node thinks the connection is still open. When node tries to write to that connection, node crashes. What's the best way to deal with this situation? -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
