On Mon, 18 Oct 2010 19:38:46 +0200, Nicholas Zakas nza...@yahoo-inc.com
wrote:
Just for my own understanding, what you're saying is:
1) Any event name in the stream must be a valid event name in that it
must not have spaces, special characters, etc. (The wording in the spec
made me think
On Tue, 19 Oct 2010 00:15:27 +0200, Daniel Cheng dch...@chromium.org
wrote:
Sorry, I'm using properties as a generic term for different types of
data that might be set in a drag. A lot of file managers try to be
helpful and
populate alternative metadata for a file. Some of this metadata
In the latest draft of Server-Sent Events, the EventSource object upholds the
same origin policy for event stream resources. Although CORS is mentioned in
the references section, it's not mentioned in the body of the spec, so I was
wondering if this has been brought up before?
The reason I
On Tue, Sep 14, 2010 at 7:49 PM, Philip Jägenstedt phil...@opera.com wrote:
On Tue, 14 Sep 2010 10:30:03 +0200, Simon Pieters sim...@opera.com wrote:
On Tue, 14 Sep 2010 10:11:16 +0200, Philip Jägenstedt phil...@opera.com
wrote:
The point of a header is that browsers can identify WebSRT
On Wed, Sep 8, 2010 at 1:19 AM, Ian Hickson i...@hixie.ch wrote:
[...] You're also excluding roll-on captions then which is a feature of
live broadcasting.
It isn't clear to me that an external file would be a good solution for
live broadcasting, so I'm not sure this really matters.
The
On Wed, Oct 20, 2010 at 9:59 AM, Odin Omdal Hørthe odin.om...@gmail.com wrote:
On Wed, Sep 8, 2010 at 1:19 AM, Ian Hickson i...@hixie.ch wrote:
[...] You're also excluding roll-on captions then which is a feature of
live broadcasting.
It isn't clear to me that an external file would be a good
