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 25096 - Mapping commands to protocol should be protocol-neutral
Summary: Mapping commands to protocol should be protocol-neutral
Status: RESOLVED INVALID
Alias: None
Product: Browser Test/Tools WG
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Browser Testing and Tools WG
QA Contact: Browser Testing and Tools WG
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20860
  Show dependency tree / graph
 
Reported: 2014-03-19 06:11 UTC by Alexei Barantsev
Modified: 2014-07-28 15:13 UTC (History)
3 users (show)

See Also:

Attachments

Description Alexei Barantsev 2014-03-19 06:11:59 UTC 
Mapping commands to protocol should be protocol-neutral and should be applicable to al least three options: HTTP, WebSocket and TCP.
Comment 1 Simon Stewart 2014-07-28 15:13:31 UTC 
Quoting from section 2.6 of the current editor's draft:

"Although the encoding and transport mechanism is left undefined in this specification, implementors of the remote end must provide an implementation suitable for acting as the server-side of the JSON and HTTP protocol (the "JSON Wire Protocol") defined in this specification"

The spec won't deal with the mapping of commands to the protocol, but instead will be written in terms of the tuple of the URL endpoint and HTTP verb.