Currently elliptics network only supports plain lookup command, which will only tell the node address where object is supposed to live in given configuraion, but it does not check whether object is actually placed there.

So, to find out precise location of the data one has to perform at least two steps - lookup a node, where it is supposed to be, and issue direct request to that node to read part of the data. It is not very effective, so plan is to extend lookup command to perform actual object 'touch' if requested.

To date I kind of implemented needed FastCGI elliptics network daemon which lookups nodes according to URL it got, but it is rather limited from configuration point of view, i.e. there is a fair number of data hardcoded in the daemon, which should actually be read from config. I plan to use various environment variables FastCGI daemon is able to read to put there remote node addresses to contact, transformation functions to use, various timeouts and so on.

Also this daeomon will be the first user of the extended lookup command (yet to be written :).

Stay tuned, I plan to complete this whole setup and implementation this week and run some tests to find out whether solution with the direct data URL instead of getting it via elliptics network API is a good idea and what problems can be found in such installation.