I have an classical apache server delivering php files, and a nodeJS server (with socket.io, but whithout express/connect) used for real-time event management on that PHP website. I sometimes need to authenticate the clients connecting to the nodeJS server, but this authentication is lost when the user reloads the page, because it also reloads the socket.io client (I store the socket ID on the server, which gets lost at each refresh) The question is: Is there a way to keep the connection alive in socket.io, or a way to link the apache PHP sessions and the nodeJS server? Or maybe a way to keep this authentication using cookies (knowing I must store sensitive data like user passwords and keys)? Though the thread is old I would like to recommend what I used for my project. Instead of memcached you can also use Redis for session handling. I have used the as php redis client.Instead of storing session to files you can save in Redis.

I want to deserialize data from php serialize array in node js I found in many questions use JSON.stringify() to serialize and for deserialize use JSON.parse but unable to do the same and not find.

Most of the heavy lifting will be done by apache. For every request apache will append the session values to the cookies.And it reads the session values from every request and validates it. Setting required to save the php session to redis is also very simple. Session.save_handler = redis session.save_path = 'tcp://host1:6379?weight=1, tcp://host2:6379?weight=2&timeout=2.5, tcp://host3:6379?weight=2' That's it. Free Books On Php Programming. Hp Pavilion G6 Recovery Partition Download more. Simon Aronson Simply Simon Pdf Printer. This will make php save the sessions to redis instead of the file. This will also move the session that are stored in files to redis.

You can.json files. Var parsedJSON = require('./file-name'); For example if you have a config.json file in the same directory as your source code file you would use: var config = require('./config.json'); or (file extension can be omitted): var config = require('./config'); note that require is synchronous and only reads the file once, following calls return the result from cache Also note You should only use this for local files under your absolute control, as it potentially executes any code within the file. @natario: We are talking about server-side JS here. Suppose someone is parsing user-supplied JSON. If the assumption is that the JSON is always well formed, an attacker can send some malformed JSON to trigger an error, which if spilled to the client side, may reveal vital information about the system. Or if the JSON was both malformed and contained some text with.