Graceful error handling while ls

[silexlabs]

Graceful error handling while ls

[KrishnaPG]

Another point worth noting is the caching behavior with www. Presently ETag support is already monitoring the ls results and server is issuing a 304 correctly !!

However, at the ground level the computation (the actual retrieval of the directory content and creating the json etc.) is still happening as a full blown request. Perhaps in the future versions, a crude caching layer can be implemented (that monitors the "if modified" request header and compares it with the 'modified time' of top level folder that is being walked.

[lexoyo]

+1

[lexoyo]

your starting to define what the a v1 should be, I like this

[KrishnaPG]

Created PR #34 that implements graceful error handling for few "ignorable errors" while doing ls() and also primitive 304 ETag support for ls().

Now ls() (for www) does not waste CPU / Disk cycles on recomputing the folder structure for already visited (and unmodified) folders. Any modifications, as usual lead to a full 200 response