9745
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
We should require nextprotoneg support when doing the TLS handshake for WebSocket.
|
2010-05-17
|
2010-08-13
|
9766
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
We should expose the subprotocol for the case of the client not specifying one but the server specifying one
|
2010-05-18
|
2010-07-22
|
9973
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
NEED
|
If the entry's name is "sec-websocket-protocol" 0 please don't put normative requirements in parenthesis
|
2010-06-21
|
2010-07-22
|
9989
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
Is the number of replacement characters supposed to be well-defined? If not this should be explicitly noted. If it is then more detail is required.
|
2010-06-23
|
2010-09-30
|
10129
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
The end of this WebSocket section links to EventSource with "fail the connection". It should link to the WebSocket "fail the connection" instead.
|
2010-07-10
|
2010-07-22
|
10985
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
The sentence "The subprotocol names must all be non-empty ASCII strings with no control characters and not spaces in them (i.e. only characters in the range U+0021 to U+007E)." should actually read: "The subprotocol names must all be non-empty ASCII strin
|
2010-10-06
|
2010-10-12
|
11570
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WONT
|
Can't find the posibility for user authentication by connecting to a websocket! Missing?
|
2010-12-17
|
2011-01-11
|
11571
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
http://mntaxwaste.blogspot.com/ what is this and where did it come from
|
2010-12-18
|
2010-12-18
|
11581
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
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-
|
2010-12-20
|
2011-01-11
|
11730
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
Please enter your feedback, carefully indicating the title of the section for which you are submitting feedback, quoting the text that's wrong today if appropriate. If you're suggesting a new feature, it's really important to say what the problem you're t
|
2011-01-11
|
2011-01-11
|
11743
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
salut je teste les websocket 123
|
2011-01-12
|
2011-01-12
|
11770
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
test tx.executeSql("SELECT COUNT(*) FROM ToDo", [], function(result){}, function(tx, error){}); tx.executeSql("SELECT COUNT(*) FROM ToDo", [], function(result){}, function(tx, error){}); tx.executeSql("SELECT COUNT(*) FROM ToDo", [], function(result){},
|
2011-01-15
|
2011-02-15
|
11834
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
API for send/receive of binary data? Current IETF protocol drafts have binary type. Consider typed arrays (ArrayBuffer).
|
2011-01-21
|
2011-05-26
|
11847
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
hich you are submitting feedback, quoting the text that's wrong today if appropriate. If you're suggesting a new feature, it's really important to say what the problem you're trying to solve is. That's more imp
|
2011-01-24
|
2011-01-24
|
11908
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
testg wefe fwefwe fweefw few fefeefw ef
|
2011-01-28
|
2011-01-28
|
11918
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
ola snjsy a sasdsadv aaxcv
|
2011-01-29
|
2011-01-29
|
11919
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
aadsasdasdasdasdsadadasdad df df afdsfdsf asfadasd
|
2011-01-29
|
2011-01-29
|
11965
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
tengo una duda respecto al uso de los webSockets
|
2011-02-02
|
2011-02-02
|
12092
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
Please enter your feedback, carefully indicating the title of the section for which you are submitting feedback, quoting the text that's wrong today if appropriate. If you're suggesting a new feature, it's really important to say what the problem you're t
|
2011-02-16
|
2011-02-16
|
12102
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
WebSocket protocol update time
|
2011-02-17
|
2011-06-14
|
12118
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
tyutyuty dgdg ddfg ddf dgf d
|
2011-02-18
|
2011-02-18
|
12180
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
NEED
|
give the name of url to download the Jetty server
|
2011-02-25
|
2011-03-24
|
12190
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
I think this will become useless because it need server to run. Kaazing.com is selling the server. Unless there is an open source server where people can use. Then it will become popular.
|
2011-02-25
|
2011-03-24
|
12206
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
Please enter your feedback, carefully indicating the title of the section for which you are submitting feedback, quoting the text that's wrong today if appropriate. If you're suggesting a new feature, it's really important to say what the problem you're t
|
2011-02-28
|
2011-02-28
|
12433
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
Define which status code and reason to use in the close frame for close(), when navigating away, and when garbage collecting an open websocket
|
2011-04-06
|
2011-05-27
|
12510
|
WebAppsW
|
WebSocke
|
glenn
|
NEW
|
---
|
Specs split off from HTML5 (like WebSockets) need to have xrefs linked, otherwise they're ambiguous
|
2011-04-16
|
2012-10-29
|
12805
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
websocket.binaryType should be a string "blob" or "arraybuffer" for consistency with XHR
|
2011-05-28
|
2011-05-31
|
12816
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WONT
|
Make second argument in constructor an object for future extensibility
|
2011-05-30
|
2011-07-07
|
12912
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
Close status code is an unsigned short
|
2011-06-08
|
2011-06-22
|
12913
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
Close() should throw the same exception as send() for unpaired surrogates
|
2011-06-08
|
2011-06-21
|
12914
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
close() should throw SYNTAX_ERR if the encoded reason string is too long (protocol supports up to 123 UTF-8 bytes)
|
2011-06-08
|
2011-06-21
|
12916
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WORK
|
Default values for code and reason when wasClean is false
|
2011-06-08
|
2011-06-21
|
12917
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WONT
|
"deflate-stream" should be an optional extension when establishing a connection
|
2011-06-08
|
2011-07-27
|
12965
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
Problem: I want to perform DNS queries from a HTML5 app, but the networking functions available are too restrictive to build a stub resolver. Why: DNS is not just for machines - zones may contain extremely useful and rich information for humans too, e.g.
|
2011-06-16
|
2011-06-21
|
12980
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
"Let origin be the ASCII serialization of the origin of the script that invoked the WebSocket() constructor, converted to ASCII lowercase." should probably say "entry script" like EventSource and other things do.
|
2011-06-17
|
2011-06-21
|
13104
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
Enable keepalive on WebSocket API
|
2011-06-30
|
2011-10-25
|
13162
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
The notes really do need to be cleaned up to be made explicit. Like WTH does this actually say? "The fail the WebSocket connection algorithm invokes the close the WebSocket connection algorithm, which then establishes that the WebSocket connection is clo
|
2011-07-06
|
2011-07-28
|
13172
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
NEED
|
The definition for [MessageEvent] is missing.
|
2011-07-07
|
2011-08-04
|
13178
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WONT
|
binaryType should be immutable after connection is established
|
2011-07-07
|
2011-07-08
|
13180
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WONT
|
[Editorial] Causes that lead to failing the WebSocket connection, which results in an error event, should be more clearly specified
|
2011-07-07
|
2011-08-06
|
13287
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
Hello! Into HTML5, i need browser to browser connection (p2p), directly! without server! Thanks.
|
2011-07-18
|
2011-07-18
|
13294
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
The send() method should fail the WebSocket connection when data cannot be sent
|
2011-07-19
|
2011-08-05
|
13295
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WONT
|
The "make disappear a WebSocket object" case should not fail the WebSocket connection
|
2011-07-19
|
2011-08-08
|
13321
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
This is amazing! Awesome for multiplayer games!
|
2011-07-21
|
2011-07-21
|
13322
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WONT
|
Add UDP! Quake uses UDP, I can't continue development of WebQuake because it uses UDP.
|
2011-07-21
|
2011-08-08
|
13525
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
Define what .origin should be for message events
|
2011-08-02
|
2011-08-08
|
13526
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
"One distinction we have decided to draw is to prevent downgrading mixed content with websockets (i.e. you cannot connect to a ws:// url from a https:// based context)." -- http://www.ietf.org/mail-archive/web/hybi/current/msg08017.html - specify this if
|
2011-08-02
|
2011-08-08
|
13700
|
WebAppsW
|
WebSocke
|
mike
|
RESO
|
FIXE
|
W3C SotD of this document still mentions whatwg.org version of the WebSocket protocol which is out of date.
|
2011-08-07
|
2012-02-07
|
13763
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WONT
|
The WebSocket API should provide a polling mechanism too. Only event based capture messages is not good because if a method in a JS-Class send a message the reply arrive in the event handler. The event handler has no access (if no global var exists) to th
|
2011-08-12
|
2011-08-13
|
13777
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
The WebSocket protocol draft (hybi-10) restricts the value of subprotocols as follows: The elements that comprise this value MUST be non- empty strings with characters in the range U+0021 to U+007E not including separator characters as defined
|
2011-08-15
|
2011-09-19
|
13984
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WORK
|
Need a way to object detect which binary formats are supported before connecting
|
2011-08-31
|
2011-09-14
|
13990
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
Need a spec for CloseEvent constructor
|
2011-09-01
|
2011-09-10
|
14057
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
In section "The WebSocket interface" when describing the operation of the WebSocket constructor, the following statement is made: "Return a new WebSocket object, and continue these steps in the background (without blocking scripts). ... Establish a WebSoc
|
2011-09-07
|
2011-09-10
|
14108
|
WebAppsW
|
WebSocke
|
ian
|
VERI
|
INVA
|
It works as expected. Thanks for making this.
|
2011-09-11
|
2011-09-16
|
14180
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
Call onclose() passing as argument the WS close frame status and status code and reason
|
2011-09-16
|
2011-09-16
|
14297
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
ja sam manijak iz gimnazijskog parka, već danima sakriven ja gledam te iz mraka
|
2011-09-26
|
2011-09-27
|
14322
|
WebAppsW
|
WebSocke
|
jackalmage
|
RESO
|
DUPL
|
Update URL of the WebSocket protocol
|
2011-09-28
|
2011-10-31
|
14395
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
asd asasd asda dasd as d
|
2011-10-06
|
2011-10-06
|
14396
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
ddfsdfsdf sdf fdsgshdf vjlh fjhvkjds hkjdfh jdsgfvslhjfdvhd
|
2011-10-06
|
2011-10-06
|
14414
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
Is it really can be used like Winsocket? How can I use it?
|
2011-10-10
|
2011-10-18
|
14474
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
Make it possible to close a connection in such a manner that all subsequent events are suppressed
|
2011-10-14
|
2011-10-31
|
14513
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
WebSocket API: Missing reference for definition of MessageEvent
|
2011-10-19
|
2011-10-25
|
14527
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
cfgdfg dfg dfg dfg fgfdg sdftgf dhfghgdhfghfgdh fgh dfhdfhfghfghghhd
|
2011-10-20
|
2011-10-20
|
14544
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the most recently formally published rev
|
2011-10-22
|
2011-10-22
|
14660
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WORK
|
[Editorial] Clarification for CLOSING in Garbage Collection
|
2011-11-01
|
2011-11-02
|
14684
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
fghfghf fgh fgh fgh fdghdffh fgh
|
2011-11-03
|
2011-11-03
|
14847
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
HTTP/1.1 101 Switching Protocols Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: nToZIrKj/IYE0NjsLns7R+Msfcg=
|
2011-11-17
|
2011-11-18
|
14848
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
HTTP/1.1 101 Switching Protocols Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: nToZIrKj/IYE0NjsLns7R+Msfcg=
|
2011-11-17
|
2011-11-18
|
15104
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WONT
|
In reply to: <p class="warning">Following HTTP procedures here could introduce serious security problems in a Web browser context. For example, consider a host with a WebSocket server at one path and an open HTTP redirector at another. Suddenl
|
2011-12-07
|
2011-12-09
|
15129
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
Vxvzvxvjbcb vs avatars Bdhzgzgagdffgx Vvgbv bb Gvvcn. Bcc cf hghvhhcygfg fscsssxaxsszzxcxs Gets es Gvvfvbvfamtsf
|
2011-12-09
|
2011-12-09
|
15209
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
REMI
|
Provide authors with a way to handle running out of buffers, if that turns out to ever actually happen in practice
|
2011-12-15
|
2012-12-31
|
15210
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
REMI
|
Consider dispatching an event when bufferedAmount drops to 0
|
2011-12-15
|
2012-12-31
|
15266
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
I m testing the websocket, Please kindly neglect
|
2011-12-19
|
2011-12-19
|
15292
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
HTTP/1.1 101 WebSocket Protocol Handshake Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Origin: http://example.com Sec-WebSocket-Location: ws://example.com/demo Sec-WebSocket-Protocol: sample
|
2011-12-21
|
2011-12-22
|
15293
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
DUPL
|
HTTP/1.1 101 Web Socket Protocol Handshake Upgrade: WebSocket Connection: Upgrade WebSocket-Origin: http://www.cnodejs.org WebSocket-Location: ws://www.cnodejs.org:8088/echo
|
2011-12-21
|
2011-12-22
|
15400
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
WebSocket Protocol reference needs updating
|
2012-01-03
|
2012-05-02
|
15595
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
The abstract could be improved by pointing out that "WebSocket protocol" is defined by the IETF, while this API specifies the browser API to use that protocol. "The send(data) method transmits data using the connection. If the readyState attribute is CONN
|
2012-01-17
|
2012-05-02
|
15829
|
WebAppsW
|
WebSocke
|
mike
|
NEW
|
---
|
wrong bug tracker ref
|
2012-02-01
|
2012-05-02
|
15830
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
DUPL
|
incorrect protocol spec ref
|
2012-02-01
|
2012-02-01
|
15973
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
For WSS, there should be no masking from client to server. Masking is only necessary for WS client to server.
|
2012-02-13
|
2012-02-13
|
16134
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
This spec should point out how to actually receive data. Afaik you need to access the message event's data property, but the spec doesn't mention that anywhere.
|
2012-02-27
|
2012-05-02
|
16157
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
WebSocket shouldn't throw SyntaxError on unpaired surrogates
|
2012-02-29
|
2012-05-02
|
16223
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WONT
|
Change .readyState to use string values rather than numeric constants
|
2012-03-04
|
2012-03-13
|
16534
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
give me a demo on php pleaseeeeeeeeeeeeeeeee!
|
2012-03-27
|
2012-03-27
|
16703
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WORK
|
I am suggesting a default value for the "code" argument to the close method. I am currently experimenting with this method and noticed that Chrome and Firefox seem to use different default values. If I do not specify a code, Chrome appears to use 1005 (
|
2012-04-11
|
2012-05-02
|
16708
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
s/ArrayBuffer/ArrayBufferView/ - See http://lists.w3.org/Archives/Public/public-webapps/2012AprJun/0177.html
|
2012-04-12
|
2012-05-02
|
16846
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
cześc to ja rodzyn i wydaje mi się ze jestem na dość dobrej pozycji i w ogóle jestem super i jestem zajebisty ale nie czaje o co chodzi ty wszystklim ludzą skoro to ma tak wyglądać no to wydaje mi się że to będzie już koniec co wyu na no to ;;;
|
2012-04-24
|
2012-04-25
|
16927
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
HTML reference was changed from W3C version to WHATWG version
|
2012-05-04
|
2012-07-20
|
16930
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WORK
|
I don't like public data
|
2012-05-04
|
2012-05-04
|
16999
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
Clarify JS type for empty close reason
|
2012-05-08
|
2012-05-10
|
17073
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
NEED
|
Formatting Binary Data
|
2012-05-16
|
2012-07-25
|
17184
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
Please don't use section numbers as these tend to change rapidly and make your feedback harder to understand.
|
2012-05-25
|
2012-05-25
|
17196
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
(Note: Your IP address and user agent will be publicly recorded for spam prevention purposes.)
|
2012-05-25
|
2012-05-25
|
17224
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
Possible typo in section 6: Ping and Pong Frames
|
2012-05-28
|
2012-07-10
|
17262
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WORK
|
send function should have async interface
|
2012-05-31
|
2012-07-10
|
17263
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
Keep on having send(ArrayBuffer data) interface in addition to send(ArrayBufferView data)
|
2012-05-31
|
2012-07-26
|
17264
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
LATE
|
Add attributes to use ping/pong frames effectively
|
2012-05-31
|
2012-10-02
|
17437
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
Doc/mim70$slowac speed x 20(x20)mack test3.Gophertext.Rouder don't it Id!
|
2012-06-07
|
2012-06-07
|
17467
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
Established in 2003, http://www.fashionskateshoes.com, was born out of the streets desire for urban biased fashion. When SUPRA,NIKE NEW BALANCE,GUCCI were causing waves in the early 2000's the fashion of hip hop and urban shoes came to the fore in a big w
|
2012-06-12
|
2012-06-12
|
17485
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
NEED
|
Whatsapp application can not connect to server
|
2012-06-14
|
2012-06-14
|
17486
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
DUPL
|
Whatsapp application can not connect to server
|
2012-06-14
|
2012-06-14
|
17644
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
OK I spent hours all over the web and your docs getting to grips with websocket, my question now is this.... in the the handshake....how does one actually implement the header for the websocket? there is not explanation of this anywhere... how is the head
|
2012-06-28
|
2012-06-29
|
17653
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
<!doctype html> <html lang="ja"> <head> <meta charset="utf-8"> <title>撮影依頼 - ちくせいロケーションサービス「ちくロケ!」</title> <meta name="description" content="下記に必要事項をご記入のうえ、送信してください。お探しのイメージを出来るだけ詳細..." /> <meta name="keywords" content="撮影依頼,ロケ地,撮影,田園地帯,学校撮影,日本家屋,墓地撮影,映画ロ
|
2012-06-29
|
2012-06-29
|
17661
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
I would like to try this input box. Thanks
|
2012-06-30
|
2012-06-30
|
17685
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
Hello, Please make the standard web socket api include a spec for an in browser "listener" socket. Meaning: a javascript application is able to create a server listener socket in the browser on the client. Another client can discover this ip (though most
|
2012-07-04
|
2012-07-25
|
17786
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
INVA
|
hello, i am just testing websocket, thank you.
|
2012-07-16
|
2012-07-16
|
18509
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
I find typo. in 4 The WebSocket interface attribute EventHandleronopen; -> attribute EventHandler onopen;
|
2012-08-09
|
2012-08-31
|
18623
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
Editorial issues: Clarify CLOSING, capitalize websocket, add anchor to reason attribute
|
2012-08-20
|
2012-08-29
|
18749
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WONT
|
Why removing exception throwing from binaryType
|
2012-08-31
|
2012-09-28
|
21147
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WONT
|
WebSocket API could provide a method to get the HTTP response code when it's not 101
|
2013-02-27
|
2013-03-04
|
23575
|
WebAppsW
|
WebSocke
|
dave.null
|
RESO
|
FIXE
|
The paragraph about patent policy is duplicated.
|
2013-10-21
|
2015-10-06
|
23576
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
Clarify what to do when received null value subprotocol in reply to non-empty subprotocol
|
2013-10-21
|
2013-10-21
|
23601
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
FIXE
|
Define a variable to replace "with prejudice"
|
2013-10-23
|
2013-11-19
|
24184
|
WebAppsW
|
WebSocke
|
contributor
|
REOP
|
---
|
References undefined type EventHandler
|
2014-01-02
|
2014-01-02
|
27915
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
WORK
|
Clients of WebSockets are not NTP synced (and there is no NTP-alike spec)
|
2015-01-28
|
2015-10-01
|
28841
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
MOVE
|
Incorporate changes suggested by Mixed Content
|
2015-06-22
|
2016-03-05
|
29397
|
WebAppsW
|
WebSocke
|
ian
|
RESO
|
MOVE
|
[imports]: Typo: s/altorighm/algorithm
|
2016-01-27
|
2016-01-27
|