This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11581 - Is there really need to drop http compability ? This will cause lot of troubles in some http-servers and browsers. This will force developers to use ugly hacks like flash/java based implementations. Is there any reason, wht not to create real robust http-
Summary: Is there really need to drop http compability ? This will cause lot of troubl...
Status: RESOLVED INVALID
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebSocket API (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: public-webapps-bugzilla
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-20 22:11 UTC by contributor
Modified: 2011-01-11 19:39 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2010-12-20 22:11:34 UTC 
Specification: http://dev.w3.org/html5/websockets/
Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#top

Comment:
Is there really need to drop http compability ? This will cause lot of
troubles in some http-servers and browsers. This will force developers to use
ugly hacks like flash/java based implementations. Is there any reason, wht not
to create real robust http-based comet standard?

Regards,
Artur Dwornik

Artur.Dwornik@gmail.com

Posted from: 62.21.52.51
Comment 1 Ian 'Hixie' Hickson 2011-01-11 19:39:26 UTC 
The protocol is no longer defined in this spec; it's defined by the hybi working group at the IETF.