PHP is designed to be ran under some apachy stuff and live for just one request. So it would indeed be simpler to keep a node.js server constantly polling server with php module in it with ajax requests.
But if this system will ever eat a lot of resources and you would like to turn it to a long-running daemon... I'd suggest to stop there and rewrite anything to node.js (or python or erlang or go or whatever). Because there're some things that PHP will never do good. On Saturday, May 18, 2013 3:05:43 PM UTC+4, [email protected] wrote: > > HTTP requests would likely be best because most existing PHP software is > designed around the HTTP request/responce model. And yes, Node vs '...' > aguments are mute when you must use existing software, especially if your > working on existing production systems. -- -- 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.
