On Wed, Aug 1, 2012 at 12:03 PM, Florian Bösch <pya...@gmail.com> wrote:
> On Wed, Aug 1, 2012 at 7:57 PM, Glenn Adams <gl...@skynav.com> wrote:
>
>> blob =
>> bb.getBlobFromURL("ws://specifiction.com/image/kitten.png<http://specifiction.com/kitten.png>
>> ")
>>
>
> There is no application layer transfer protocol inherent in websockets.
> Requesting a resource does not have any inherent meaning other than that
> you are opening a "channel" onto /image/kitten.png. Whoever receives that
> request is free to respond to that however he likes. You would need to
> introduce an application layer content protocol on top of websockets, and
> introduce a default websocket server framework capable of understanding
> such content requests. You're not just extending lazy reading to
> websockets. You're putting the burden on yourself to also specify a
> completely new standard application layer protocol for transfer and range
> and acquisition of resources over websocket channels.
>
So? Why should lazy blob be specific to HTTP specific semantics when an
arbitrary URL is not specific to HTTP?
