[Bug 11836] Don't specify the transport, just specify API and protocol


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX
           Severity|major                       |normal

--- Comment #15 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-06-21 05:23:38 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:

Status: Rejected
Change Description: no spec change
Rationale: If people want to use this protocol in other situations for which it
is not well suited and for which it was not designed, that's their business,
but that doesn't mean we should change the API so that it makes handling those
cases easier. If anything, it's better that the API be less suitable for those
cases, as it would discourage it.

Reductio ad absurdum: if someone were to use this protocol to communicate
between two chips on a  cat food dispenser microcontroller, should we change
the API and protocol to have a field for listing the number of cats? No, we
should tell them that they're making a mistake.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Tuesday, 21 June 2011 05:23:41 UTC