Serialization & Deserialization about limdu

[erelsgl]

Hi Kai,

The function serialize.toString does not automatically generate a json file. It only returns a string.

To save the string to a file, you can use the standard writeFile or writeFileSync function of the fs library, see here:
https://nodejs.org/api/all.html#all_fs_writefile_filename_data_options_callback

For example:

var fs = require('fs');  
var classifierString = serialize.toString(intentClassifier, newClassifierFunction);
fs.writeFileSync("myFileName.json", classifierString);

[kafechew]

You're so cool!

Let's say I had saved the string to "myFileName.json" as suggested...
and send into remote server folder, "/myFolder".
How to initialize the deserialization?

My guess:

var intentClassifierCopy = serialize.fromString(intentClassifierString, myFolder/myFileName.json);

Am I right?

Thanks again!

[erelsgl]

In order to deserialize, you first have to read the string from the file, like this:

var intentClassifierString = fs.readFileSync("myFolder/myFileName.json");
var intentClassifierCopy = serialize.fromString(intentClassifierString, __dirname);

[kafechew]

Working great!
I had migrated from natural to limdu!
Thank you very much!

[kafechew]

@erelsgl
The above, we will store the .json files as local files in the remote server.
What if the .json file is an external file, not a local file?
Instead of moving the files to remote server, can the remote server directly call the .json from the original server?

Can we deserialise the external .json (http://anotherweb.com/json/myFileName.json) ?

My guess:

var __dirname = "http://anotherweb.com/json";
var intentClassifierString = fs.readFileSync("myFileName.json");
var intentClassifierCopy = serialize.fromString(intentClassifierString, __dirname);

Can you confirm that?
Thanks in advanced.

[erelsgl]

Hi Kai,

I think readFileSync works only with local files.

To download a remote file, try the suggestions here:
http://stackoverflow.com/questions/11944932/how-to-download-a-file-with-node-js

On Mon, Apr 27, 2015 at 5:29 PM, Kai Chew [email protected] wrote:

Reopened #25 #25.

—
Reply to this email directly or view it on GitHub
#25 (comment).

[kafechew]

@erelsgl
You're right. Just solved through alike method as you suggested, i.e. xhr
Things are interesting now!
Thanks again!! :-)