On Thu, Feb 23, 2012 at 12:58 PM, Feras Moussa wrote:
> This isn't clear from the spec (And I've made a note to clarify it) but
> URLs for
> streams should be one time use URLs (once used it should be automatically
> revoked).
Is it always possible to define that in a sane way?
For example, w
On 02/23/2012 12:58 AM, Feras Moussa wrote:
-Original Message-
From: Stefan Hakansson LK [mailto:stefan.lk.hakans...@ericsson.com]
Sent: Sunday, February 05, 2012 4:50 AM
To: Feras Moussa
Cc: Travis Leithead; public-webapps@w3.org
Subject: Re: StreamBuilder threshold
On 01/26/2012 07:05
> -Original Message-
> From: Stefan Hakansson LK [mailto:stefan.lk.hakans...@ericsson.com]
> Sent: Sunday, February 05, 2012 4:50 AM
> To: Feras Moussa
> Cc: Travis Leithead; public-webapps@w3.org
> Subject: Re: StreamBuilder threshold
>
> On 01/26/2012 07:0
On 01/26/2012 07:05 PM, Feras Moussa wrote:
Can you please clarify what scenario you are looking at regarding
multiple consumers? When designing the StreamBuilder API, we looked
at it as a more primitive API which other abstractions (such as
multiple consumers) can be built upon.
(Please forgiv
On Thu, 26 Jan 2012 19:05:05 +0100, Feras Moussa
wrote:
When designing the StreamBuilder API, we looked at it as a more
primitive API which other abstractions (such as multiple consumers) can
be built upon.
We should not have a StreamBuilder API. We should have a Stream
constructor, simi
Can you please clarify what scenario you are looking at regarding multiple
consumers?
When designing the StreamBuilder API, we looked at it as a more primitive API
which other abstractions (such as multiple consumers) can be built upon.
If you can please let me know what issue you're trying to
