On Sat, 05 Jan 2008 07:51:29 +0100, Henry Mason [EMAIL PROTECTED] wrote:
There's recently been some talk about completely removing HTML 5 section
6.2, Server-sent DOM events. I propose that rather than remove, we
revise.
I agree that we should keep it.
- Continued problems of the 2
Henry Mason [EMAIL PROTECTED] wrote:
There's recently been some talk about completely removing HTML 5
section 6.2, Server-sent DOM events. I propose that rather than
remove, we revise.
The major concerns I've heard about section 6.2 include:
- Unnecessary dependency on DOM Events
Anne van Kesteren wrote:
- Continued problems of the 2 connection limit on HTTP server
scalability
Is there any realistic solution to this other than to use separate
domains and have cross-domain working?
Simply get rid of, or significantly raise, the limit? Standards work
related to this
Dan Mosedale wrote:
Anne van Kesteren wrote:
- Continued problems of the 2 connection limit on HTTP server
scalability
Is there any realistic solution to this other than to use separate
domains and have cross-domain working?
Simply get rid of, or significantly raise, the limit? Standards
On Sat, 05 Jan 2008 06:51:29 -, Henry Mason [EMAIL PROTECTED] wrote:
- Unnecessary dependency on DOM Events
This feature is inherently event-based. I think it does make sense to
re-use existing framework for event handling.
However, I haven't found use-case for remote triggering of
There's recently been some talk about completely removing HTML 5
section 6.2, Server-sent DOM events. I propose that rather than
remove, we revise.
The major concerns I've heard about section 6.2 include:
- Unnecessary dependency on DOM Events
- Redundancy with already existing techniques,
