Monthly Archives: آبان 1392

which data structure stores data in "type:length:value" triplets?

Leave a reply

Salam (means Hello) :)

parsing output of a third party script, which was stored in a MySQL database, I encountered data structures almost like JSON, but in a triplets of:

key_type:key_length:key_name;
value_type:value_length:value_contents;

this is a example of it:

a:1:{
    s:5:"title";
    s:28:"<div>This is item title</div>";
    s:9:"permalink";
    s:31:"http://example.com/post-88.aspx";
    s:7:"content";
    s:31:"<div>This is item content</div>";
    s:4:"meta";
    a:1:{
        s:4:"tags";
        s:22:"these, are, some, tags";
    }
}

I just want to know is this a common standard structure or something conventional created by this script developers?

which data structure stores data in "type:length:value" triplets?

Leave a reply

Salam (means Hello) :)

parsing output of a third party script, which was stored in a MySQL database, I encountered data structures almost like JSON, but in a triplets of:

key_type:key_length:key_name;
value_type:value_length:value_contents;

this is a example of it:

a:1:{
    s:5:"title";
    s:28:"<div>This is item title</div>";
    s:9:"permalink";
    s:31:"http://example.com/post-88.aspx";
    s:7:"content";
    s:31:"<div>This is item content</div>";
    s:4:"meta";
    a:1:{
        s:4:"tags";
        s:22:"these, are, some, tags";
    }
}

I just want to know is this a common standard structure or something conventional created by this script developers?

Node.js Unhandled ‘error’ event when using http.createServer().listen() on Ubuntu 12.04

Leave a reply

Salam (means Hello) :)

I've developed a node.js script on my windows seven machine and it's working fine. but when I run it on my Ubuntu 12.04, the following error shows up and halts my app:

    throw er; // Unhandled 'error' event
              ^
Error: listen EACCES
    at errnoException (net.js:901:11)
    at Server._listen2 (net.js:1020:19)
    at listen (net.js:1061:10)
    at Server.listen (net.js:1127:5)
    at Object.start (/httpServer/httpServer.js:9:34)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)

and the point that caused error is .listen(80) in this line:

http.createServer(onRequest).listen(80); 
                             ^

I've also tried some other port numbers (like 100, 300, 500,...) instead of 80 and the error was still the same.

Destructive young man shoots a cow in head and the old farmer says it’s OK

Leave a reply

I remember a scene from a movie where a destructive young man who is in the middle of some sort of journey, reaches a farm with many cows and shoots one of them in the head, just because it calm hims down.

Then the old farmer comes close to young man and says: "It's OK son. Come and try another one."

By the next morning, almost all the cows are dead, and the young man who is almost crying gives his gun to the farmer as a thank you.

I really loved this film, and this scene is all I remember from it. Anyone know which film this is?

Node.js Unhandled ‘error’ event when using http.createServer().listen() on Ubuntu 12.04

Leave a reply

Salam (means Hello) :)

I've developed a node.js script on my windows seven machine and it's working fine. but when I run it on my Ubuntu 12.04, the following error shows up and halts my app:

    throw er; // Unhandled 'error' event
              ^
Error: listen EACCES
    at errnoException (net.js:901:11)
    at Server._listen2 (net.js:1020:19)
    at listen (net.js:1061:10)
    at Server.listen (net.js:1127:5)
    at Object.start (/httpServer/httpServer.js:9:34)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)

and the point that caused error is .listen(80) in this line:

http.createServer(onRequest).listen(80); 
                             ^

I've also tried some other port numbers (like 100, 300, 500,...) instead of 80 and the error was still the same.