Re: [whatwg] audio and video: volume and muted as content attributes?

2010-06-01 Thread Silvia Pfeiffer
On Tue, Jun 1, 2010 at 3:53 PM, Philip Jägenstedt phil...@opera.com wrote: On Mon, 31 May 2010 19:33:45 +0800, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: Hi, I just came across a curious situation in the spec: IIUC, it seems the @volume and @muted attributes are only IDL attributes

Re: [whatwg] audio and video: volume and muted as content attributes?

2010-06-01 Thread Philip Jägenstedt
On Tue, 01 Jun 2010 14:17:03 +0800, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: On Tue, Jun 1, 2010 at 3:53 PM, Philip Jägenstedt phil...@opera.com wrote: On Mon, 31 May 2010 19:33:45 +0800, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: Hi, I just came across a curious situation

[whatwg] WebSockets: UDP

2010-06-01 Thread Erik Möller
The use case I'd like to address in this post is Real-time client/server games. The majority of the on-line games of today use a client/server model over UDP and we should try to give game developers the tools they require to create browser based games. For many simpler games a TCP based

Re: [whatwg] audio and video: volume and muted as content attributes?

2010-06-01 Thread Bjartur Thorlacius
On 5/31/10, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: On Tue, Jun 1, 2010 at 6:48 AM, bjartur svartma...@gmail.com wrote: I just came across a curious situation in the spec: IIUC, it seems the @volume and @muted attributes are only IDL attributes and not content attributes. This means that

Re: [whatwg] WebSockets: UDP

2010-06-01 Thread Kornel Lesinski
On 1 Jun 2010, at 11:12, Erik Möller wrote: The use case I'd like to address in this post is Real-time client/server games. The majority of the on-line games of today use a client/server model over UDP and we should try to give game developers the tools they require to create browser

Re: [whatwg] WebSockets: UDP

2010-06-01 Thread Philip Taylor
On Tue, Jun 1, 2010 at 11:12 AM, Erik Möller emol...@opera.com wrote: The use case I'd like to address in this post is Real-time client/server games. The majority of the on-line games of today use a client/server model over UDP and we should try to give game developers the tools they require

Re: [whatwg] audio and video: volume and muted as content attributes?

2010-06-01 Thread Silvia Pfeiffer
On Tue, Jun 1, 2010 at 9:09 PM, Bjartur Thorlacius svartma...@gmail.com wrote: On 5/31/10, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: On Tue, Jun 1, 2010 at 6:48 AM, bjartur svartma...@gmail.com wrote: I just came across a curious situation in the spec: IIUC, it seems the @volume and

Re: [whatwg] audio and video: volume and muted as content attributes?

2010-06-01 Thread Lachlan Hunt
On 2010-06-01 13:09, Bjartur Thorlacius wrote: On 5/31/10, Silvia Pfeiffersilviapfeiff...@gmail.com wrote: I am not aware of a CSS property for media elements that lets you control the muted state. Can you link me to a specification? Well, http://www.w3.org/TR/CSS2/aural.html defines volume

Re: [whatwg] WebSockets: UDP

2010-06-01 Thread Erik Möller
On Tue, 01 Jun 2010 13:34:51 +0200, Philip Taylor excors+wha...@gmail.com wrote: On Tue, Jun 1, 2010 at 11:12 AM, Erik Möller emol...@opera.com wrote: The use case I'd like to address in this post is Real-time client/server games. The majority of the on-line games of today use a

Re: [whatwg] audio and video: volume and muted as content attributes?

2010-06-01 Thread Boris Zbarsky
On 6/1/10 7:09 AM, Bjartur Thorlacius wrote: Also @media aural {display: none;} can be used on audio elements but I haven't read the specs properly so I don't know if that would hide anvideo element when inside of an @media aural clause. You seem to be somewhat confused about the way media

Re: [whatwg] WebSockets: UDP

2010-06-01 Thread Mike Belshe
On Tue, Jun 1, 2010 at 4:24 AM, Kornel Lesinski kor...@geekhood.net wrote: On 1 Jun 2010, at 11:12, Erik Möller wrote: The use case I'd like to address in this post is Real-time client/server games. The majority of the on-line games of today use a client/server model over UDP and we

Re: [whatwg] WebSockets: UDP

2010-06-01 Thread John Tamplin
On Tue, Jun 1, 2010 at 11:34 AM, Mike Belshe m...@belshe.com wrote: FYI: SCTP is effectively non-deployable on the internet today due to NAT. +1 on finding ways to enable UDP. It's a key missing component to the web platform. But there is so much infrastructure that would have to be

Re: [whatwg] WebSockets: UDP

2010-06-01 Thread Mike Belshe
On Tue, Jun 1, 2010 at 8:52 AM, John Tamplin j...@google.com wrote: On Tue, Jun 1, 2010 at 11:34 AM, Mike Belshe m...@belshe.com wrote: FYI: SCTP is effectively non-deployable on the internet today due to NAT. +1 on finding ways to enable UDP. It's a key missing component to the web

Re: [whatwg] WebSockets: UDP

2010-06-01 Thread Erik Möller
On Tue, 01 Jun 2010 18:45:51 +0200, Mike Belshe m...@belshe.com wrote: On Tue, Jun 1, 2010 at 8:52 AM, John Tamplin j...@google.com wrote: On Tue, Jun 1, 2010 at 11:34 AM, Mike Belshe m...@belshe.com wrote: FYI: SCTP is effectively non-deployable on the internet today due to NAT. +1 on

Re: [whatwg] WebSockets: UDP

2010-06-01 Thread Philip Taylor
On Tue, Jun 1, 2010 at 2:00 PM, Erik Möller emol...@opera.com wrote: [...] I've never heard any gamedevs complain how poorly UDP matches their needs so I'm not so sure about that, but you may be right it would be better to have a higher level abstraction. If we are indeed targeting the game

Re: [whatwg] WebSockets: UDP

2010-06-01 Thread Erik Möller
On Tue, 01 Jun 2010 21:14:33 +0200, Philip Taylor excors+wha...@gmail.com wrote: More feedback is certainly good, though I think the libraries I mentioned (DirectPlay/OpenTNL/RakNet/ENet (there's probably more)) are useful as an indicator of common real needs (as opposed to edge-case or

Re: [whatwg] audio and video: volume and muted as content attributes?

2010-06-01 Thread Bjartur Thorlacius
References: aanlktilyqfgvi5azyr4zpxjiqctl7gickfhzpev6g...@mail.gmail.com 4c0420c9.d345d80a.5c04.d...@mx.google.com aanlktimlhyxmzs7ujxsuacaj90dufk3advpej3uo1...@mail.gmail.com aanlktin3iq_ahiwwuwam6hevnss1rxal17g3zj9yn...@mail.gmail.com Bjartur Thorlacius

Re: [whatwg] WebSockets: UDP

2010-06-01 Thread James Salsman
I agree UDP sockets are a legitimate, useful option, with applications far beyond games. In most cases TCP is fine, but adaptive bit-rate vocoders, for example, can use packet loss as an adaptation parameter, and chose only to retransmit some of the more essential packets in cases of congestion.

Re: [whatwg] [hybi] WebSockets: UDP

2010-06-01 Thread Mark Frohnmayer
On Tue, Jun 1, 2010 at 1:02 PM, Erik Möller emol...@opera.com wrote: I was hoping to be able to avoid looking at what the interfaces of a high vs low level option would look like this early on in the discussions, but perhaps we need to do just that; look at Torque, RakNet etc and find a least

Re: [whatwg] [hybi] WebSockets: UDP

2010-06-01 Thread Scott Hess
On Tue, Jun 1, 2010 at 4:07 PM, Mark Frohnmayer mark.frohnma...@gmail.com wrote: On Tue, Jun 1, 2010 at 1:02 PM, Erik Möller emol...@opera.com wrote: So, what would the minimal set of limitations be to make a UDP WebSocket browser-safe? -No listen sockets Only feedback here would be I think

Re: [whatwg] [hybi] WebSockets: UDP

2010-06-01 Thread Mark Frohnmayer
On Tue, Jun 1, 2010 at 4:35 PM, l.w...@surrey.ac.uk wrote: On 2 Jun 2010, at 00:07, Mark Frohnmayer wrote: A single UDP socket can host multiple connections (indexed by packet source address), so even a modest limit on actual number of sockets wouldn't be a big impediment. Um, NAT? You

Re: [whatwg] [hybi] WebSockets: UDP

2010-06-01 Thread Ben Garney
On Tue, Jun 1, 2010 at 5:12 PM, Mark Frohnmayer mark.frohnma...@gmail.comwrote: On Tue, Jun 1, 2010 at 4:35 PM, l.w...@surrey.ac.uk wrote: On 2 Jun 2010, at 00:07, Mark Frohnmayer wrote: A single UDP socket can host multiple connections (indexed by packet source address), so even a modest

[whatwg] ISSUE-86, Re: hixie: Remove the HTML-to-Atom mapping definition from the W3C version of the spec. (whatwg r5100)

2010-06-01 Thread Julian Reschke
Hi Ian, thanks for the removal. I notice that you kept the text in the WHATWG version of the spec. Various problems have been reported with respect to the mapping, notably http://www.w3.org/Bugs/Public/show_bug.cgi?id=7806 and http://www.w3.org/Bugs/Public/show_bug.cgi?id=9546 and in