This may not be what you need exactly, but simple HTTP communication could
work as well. Your PHP app could do a simple curl request to a local path
provided by your node process. Any data needed to be passed between could
be sent with the request.
Once the PHP process got a 200 / {started: true} type response from your
node app, the PHP script could carry on with its business (say, serving a
response to your user) while the Node app continues the work given to it
asynchronously.
(We run numerous microapps based on Node that are (in part) consumed by our
legacy apps. Our PHP applications utilize these microapps for data
read/writes in a similar way as it would ask MySQL or Memcached for data.
Sure HTTP has more overhead than some other options we could use, but it
allows us to have specialized servers serving the node processes in a way
that is scalable at a different rate than the primary apps, and the APIs
are reusable across multiple services.)
On Monday, April 30, 2012 11:06:50 AM UTC-6, sparky wrote:
>
> 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!
>
On Monday, April 30, 2012 11:06:50 AM UTC-6, sparky wrote:
>
> 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
