Re: [filesystem-api] Observable is not appropriate for directory listing; async iterable would be better (#4)

Correct me if I'm totally wrong on this, but it honestly does seem like both can be used for the primary use cases:

1. Enumerate ONLY files, deep through the containment hierarchy, "discarding" directory results (e.g. enumerateDeep()).

2. Do something useful only upon encountering certain types of results (e.g., only *.jpeg or *.txt; only binary data, only texture data etc.) regardless of containment hierarchy, but determine all results volume.

"Observable" lent itself to filtering and mapping. I think the pace at which work is performed is dependent on a few things. Then there's backpressure too, which I'm not 100% clear on :-(

But async iterables look totally usable. 

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/filesystem-api/issues/4#issuecomment-106677109