On Wed, Aug 1, 2012 at 1:36 PM, Florian Bösch <pya...@gmail.com> wrote:
> On Wed, Aug 1, 2012 at 9:26 PM, Glenn Adams <gl...@skynav.com> wrote: > >> So? Why should lazy blob be specific to HTTP specific semantics when an >> arbitrary URL is not specific to HTTP? >> > > So if you want to have a lazy reader on Websockets you have either: > 1) respecify the websocket protocol to include content semantics for > accessing resources defined by an URL and having a specified size OR > 2) define an additional protocol on top of websockets, which websockets > know nothing about, that allows a custom implementation at the server side > to respond in a meaningful fashion to resource range requests. > OR define a mechanism for LazyBlob that permits the injection of app specific code into the underlying LazyBlob reader loop.