Develop sugar syntax and make it possible to write code more easily.

var jf = require('json.filed');

jf.filed('./hello.json')
.io( function(json,filePath) {
  return {msg: "hello" }; }) // write 1st greeting to data.json
.link( function(json,filePath){
  return 'linked_hello.json'
}).exec();

in and out, restricted derived feature of io executer would make it easier to write program.

I'm not sure to implement .delete yet.

Now in httpserve feature, JSON is responded to request of any HTTP methods.
Considering preference for RESTful concept, respond only to GET method.

Possible to say a case of calledBack use internally. A kind of syntactic sugar.

At beginning stage, setTimeout was used everywhere in test programs to wait writing process done before reading process.
This coding causes annoying error in test due to timing when node works slow.

At that time, this coding, using setTimeout, was needed because neither chained processing nor called back executed was not developed, but now it is just an obstacle.

Writing mapReduce_like.js , I found several points to consider about.
https://github.com/7k8m/json.filed/blob/master/examples/mapReduce_Like.js

Distributed processing like MapReduce have "master node" to unite each worker node.
Is it always needed ...? Answer might be yes ...

Thinking server like use of json.filed and idea of event executer.

What is difficult for event executer is that file is not fixed before event is fired.
This difficulty affects collect executer and roots executer.

Meaning directory of file system. Now json.filed do almost nothing for directory.
Just accepting path containing String of directory.

I think to consider what feature is possible.

In some cases, orphaned file prohibits collect executer to work.
It may be needed a way for programmer explicitly remove a file in process from runtime

It would be useful in operating use case.