In particular, see this post from Matt Pardee

I faced a similar problem with wanting to keep users informed of a new note added on to a bug, and similar notifications that could really only be effectively sent from PHP to my Node server. What I did follows (apologies if this gets all garbled and unformatted in sending, if it does, I d be happy to paste the code somewhere else): First, you ll need to use cURL from PHP. I wrote a function for my class like this:

function notifyNode($type, $project_id, $from_user, $data) {
    $ch = curl_init();

    curl_setopt($ch, CURLOPT_URL,  http://127.0.0.1 );

    curl_setopt($ch, CURLOPT_HEADER, 0);
    curl_setopt($ch, CURLOPT_HTTPHEADER, array( Expect: ));
    curl_setopt($ch, CURLOPT_PORT, 8001);
    curl_setopt($ch, CURLOPT_CONNECTTIMEOUT, 2);

    curl_setopt($ch, CURLOPT_POST, true);

    $pf = array( f  => $type,  pid  => $project_id,  user_from  => $from_user, 
              data  => array());

    foreach($data as $k => $v) {
        $pf[ data ][$k] = $v;
    }

    curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($pf));

    curl_exec($ch);
    curl_close($ch);
}

You ll notice that I send the cURL request on the same server since both PHP and NodeJS are running there, your mileage may vary. The port I set this code to connect to is 8001 (this is the port my Node server is running on, and the port the socket.io server connects to). This sends a HTTP POST request with the post field encoded. This is all pretty standard cURL stuff.

在您的诺言中,你也许有这样的东西:

var server = http.createServer(function(req, res) {});
server.listen(8001);
var io = io.listen(server, { transports: [ websocket ,  flashsocket ,  xhr-polling ] });

...

well what we ll do here is expand on the http.createServer part, to listen for connections coming from our local host ("127.0.0.1"). The createServer code then becomes:

var server = http.createServer(function(req, res) {
    // Check for notices from PHP
    if(res.socket.remoteAddress ==  127.0.0.1 ) {
        if(req.method ==  POST ) {
            // The server is trying to send us an activity message

            var form = new formidable.IncomingForm();
            form.parse(req, function(err, fields, files) {

                res.writeHead(200, [[ "Content-Type", "text/plain"]
                        , ["Content-Length", 0]
                        ]);
                res.write(  );
                res.end();

                //sys.puts(sys.inspect({fields: fields}, true, 4));

                handleServerNotice(fields);                
            });
        }
    }
});

您可以履行你的职责。 服务器诺言功能。

function handleServerNotice(data) {
        ...
}

etc etc. I haven t tested this in a while, and in fact that code block was commented out on my node server, so I hope what I ve pasted here works - in general this concept is proven and I think it ll work for you. Anyway just wanted to be sure you knew it s been a few months so I m not sure exactly why I commented out. The code I wrote took a little research -- like setting the Expect: header in cURL -- and I was pretty excited when it finally worked. Let me know if you need any additional help.

最好

Matt Pardee

A bit late, but you could communicate with your node client using the Redis Pub/Sub mechanism in a very simple and effective way. All you need to do is install redis on your server.

在营地方面,最初的Redis公司随后发表了信息。

$purchase_info = json_encode(array( user_id  =>$user_id,
          purchase_information =>array( item => book , price => 2$ ));

$this->redis->publish( transaction_completed , $purchase_info);

no

var redis = require( redis );
var purchase_listener = redis.createClient();
purchase_listener.subscribe( transaction_completed );
purchase_listener.on( message , function(channel, message){
    var purchase_data = JSON.parse(message);
    user_id = purchase_data.user_id;
    purchase_info = purchase_data.purchase_information;
    // Process the data
    // And send confirmation to your client via a socket connection
})

www.un.org/spanish/ecosoc 这是否可衡量? (针对@mohan-singh)

When talking about scalability you need to think about your infrastructure s architecture and your particular needs but here s a quick answer : I ve been using a variant of this mechanism on a high traffic real-time application without problems but here s what you should be careful about:

1. Redis PUB/SUB并不是一个排队系统,这意味着如果你的节点程序推翻发出的所有电文,就会丢失。

2. 如果你们有1个以上的订阅者,他们都会收到同样的信息,并处理这些信息,那么,如果你听从处理你实时逻辑的同一重新分类程序,就会小心谨慎。 (尽管如此,容易走过路)

这一制度的一点是,你不需要给你现有的基础设施增加任何东西,而且能够立即启动,它速度非常快,它完全像一个吉大港定居地的服务器。

下面是你们选择更可衡量的选择:

我个人对红斯办法的印象:umber。 你们需要管理阿帕奇、诺德JS和红利,三个服务器也一样。 而PubSub机制与提要有很大不同。 io,因此,你需要看看这是否符合你现有的法典。