Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

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.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7091421
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 28, 20262026-05-28T08:11:00+00:00 2026-05-28T08:11:00+00:00

I use socket.io version 0.8.4 I have boiled down my problem to the following.

  • 0

I use socket.io version 0.8.4

I have boiled down my problem to the following. I have data looking like this:

data.prop1 = [];
data.prop1.push("man");
data.prop2 = [];
data.prop2["hey"] = "man";

I send the data from the server to the client this way:

socket.emit("data", data);

On the client side I receive the data this way:

socket.on("data", function(data){ console.log(data); });

The weird thing is:

data.prop1 = [];
data.prop1.push("man"); // This data exists in the client side data object
data.prop2 = [];
data.prop2["hey"] = "man"; // This data does not exist.

data.prop2 is just an empty array on the client side.

Is there a known bug in json serializing arrays on the form in prop2?

Thankyou in advance

EDIT:

Problem solved using this workaround:

data.prop1 = [];
data.prop1.push("man");
data.prop2 = {}; // <= Object instead of array
data.prop2["hey"] = "man";
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-28T08:11:00+00:00Added an answer on May 28, 2026 at 8:11 am

    ECMA-262 about JSON.stringify:

    The representation of arrays includes only the elements between zero and array.length – 1 inclusive. Named properties are excluded from the stringification.

    Arrays are supposed to have numerical property names. So when the data.prop2 is transformed to JSON (which socket.io sends the data in, I imagine), it doesn’t get the 'hey' property. If you want to use non-numerical property names, you should use objects instead of arrays:

    data.prop1 = [];
    data.prop1.push("man");
    data.prop2 = {}; // Notice we're creating an object, not an array.
    data.prop2["hey"] = "man"; // Alternatively: data.prop2.hey = "man"
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I use node.js and socket.io. I am using the latest version socket.io. I have
I have a socket application which I can use in local network, at home.
Looking at examples about socket programming, we can see that some people use AF_INET
I'm using Socket.IO on Node.js. The Example here: http://socket.io/#how-to-use First Example. I have tested
I tried to send a packet on the socket I use to listen for
I am trying to use the code from Microsoft for an Async Socket connection.
How should I determine what to use for a listening socket's backlog parameter? Is
When using socket in the UNIX domain, it is advisable to use path name
Creating a server-side socket will fail if I'm trying to use the same port
I am currently doing some socket programming using C/C++. To be able to use

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.