Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Currently, I serialize a large javascript object and post it to the server. This process takes to long. So, I would like to pass a javascript object from the client to the server via node.js/socket.io so the server can handle the workload. It seems that it does not work. Is this possible?
Where is the slowdown? If the performance issue is related to serialization, then you’re faced with the same problem no matter how you communicate with the server – can’t ship objects around without serializing them first.
(To send the object over socket.io, first serialize it, then send it across as a string)