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

I just want to make sure I understand the constraints here:

1. You want the general benefits of a composable, first-class object representing the directory list. (all of the proposed options satisfy this requirement, as far as I can tell)
2. You want the producer to stop producing values if the consumer isn't ready for more. A consumer can use this infrastructure to take values one at a time, or to cache the values until it reaches a maximum number of entries it's willing to cache.
3. You want this control to be composable across the usual combinators. The consumer of `directories.map(cb)` should be able to influence the original producer.
4. The producer has some way of pausing production that is more efficient than a userland buffer. This may involve allowing the kernel to buffer the data, asking an upstream producer to stop producing data, stopping to make pull requests of an upstream producer, or a userland strategy that aggregates the buffers of multiple lists.

Did I miss anything?

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