Re: [streams] How will ReadableByteStream work with seekable resources? (#253)

I'd like to do some survey and create a table of APIs and their characteristics (sync/async, blocking/nonblocking, bring our own buffer/returns API allocated buffer, pull and read are separate/pull and read are combined, ...). Includes some non software API stuff for metaphor.

- pull without size arg + pause
    - XON/XOFF
- pull without size arg
    - returns API allocated buffer
        - XMLHttpRequest (each HTTP transaction viewed as pull)
- pull with size arg
    - TCP (pull: ACK packet, receiver window update)
    - HTTP/2 flow control (pull: WINDOW_UPDATE)
    - bring your own buffer
        - fread(3) (pull/read: fread)
        - Win32 ReadFile() (pull/read: ReadFile)
- always pull + manual pause
    - Ethernet PAUSE frame
- always pull but with backpressure
    - tap water (backpressure: turning off a faucet)
    - socket: epoll(7) + read(2)
- always pull without backpressure
    - WebSocket
    - XMLHttpRequest (response body receiving)


---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/253#issuecomment-74116107