10127
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
EventSource does not need to deal with HTTP 3xx responses as they are dealt with by the fetching algorithm.
|
2010-07-10
|
2010-08-30
|
10128
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
Step 4 of the EventSource algorithm should reference the "fail the connection" algorithm.
|
2010-07-10
|
2010-08-30
|
10130
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
INVA
|
The steps to "dispatch the event" within EventSource should first remove the LF from the data buffer before checking whether it is empty. Otherwise it can never be empty.
|
2010-07-11
|
2010-08-31
|
10131
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
Please make it clear that Last-Event-ID has a value that consists of UTF-8 octets. HTTP headers do not have strings.
|
2010-07-11
|
2010-09-08
|
11619
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
INVA
|
who is the president of the United States?
|
2010-12-30
|
2010-12-30
|
11669
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
WONT
|
Section: "Parsing an event stream" It looks like their is a mistake in this ABNF description, "end-of-line" is repeated: stream = [ bom ] *event event = *( comment / field ) end-of-line comment = colon *any-char end-of-line field
|
2011-01-05
|
2011-02-07
|
11835
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
EventSource must support cross-domain requests (ala CORS)
|
2011-01-21
|
2011-06-18
|
11836
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
WONT
|
Don't specify the transport, just specify API and protocol
|
2011-01-21
|
2011-06-21
|
12202
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
INVA
|
<html> <head> <link rel="apple-touch-icon" href="img/icons/iphone_icon.png"/> <link rel='stylesheet' type='text/css' href='http://uni104.tr.ogame.org/game/css/01style.css' media='screen' /> <link rel='stylesheet' type='text/css' href=
|
2011-02-27
|
2011-02-28
|
12411
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
eventsource: in "dispatch the event", step 3, looks like "Otherwise" is bogus and should be removed.
|
2011-04-03
|
2011-06-17
|
12883
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
WONT
|
In section headed: Interpreting an event stream Step 4: "If the event name buffer has a value other than the empty string, change the type of the newly created event to equal the value of the event name buffer." I think you mean "change the *name*" rathe
|
2011-06-03
|
2011-06-21
|
13071
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
"Once the end of the file is reached, the user agent must dispatch the event one final time, as defined below" means an implementation may parse a partial (corrupt) event as a final event if the connection is interrupted. Spec should always require an exp
|
2011-06-27
|
2011-08-04
|
13155
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
The security considerations section needs to be updated to take CORS into account.
|
2011-07-06
|
2011-08-04
|
13156
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
The charset parameter is now an optional parameter (even though it can only be set to UTF-8). That should probably be stated here.
|
2011-07-06
|
2011-08-04
|
13229
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
WORK
|
The following text from the "Security considerations" part of "11 IANA considerations" is wrong: "An event stream from an origin distinct from the origin of the content consuming the event stream can result in information leakage. To avoid this, user agen
|
2011-07-13
|
2011-08-04
|
13742
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
INVA
|
Please don't use section numbers as these tend to change rapidly and make your feedback harder to understand.
|
2011-08-10
|
2011-08-10
|
13743
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
INVA
|
Please don't use section numbers as these tend to change rapidly and make your feedback harder to understand.
|
2011-08-10
|
2011-08-10
|
13761
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
Now that event data can be discarded (if there is no newline before eof), the last id field value received should be stored in a buffer and set as the EventSource's lastEventId only when the event is actually dispatched. That way the id associated with th
|
2011-08-11
|
2011-10-11
|
13786
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
Drop the charset parameter or made it non-conforming. Other MIME types introduced by this specification do not allow the charset parameter.
|
2011-08-15
|
2011-12-07
|
13792
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
WONT
|
Remove all notes about sharing the connection. It can't work since what's received may depend on the request. It's also not reasonable to buffer every event in case they have to be dispatched again.
|
2011-08-16
|
2011-09-01
|
13794
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
WONT
|
I think length-prefixed messages would be a lot more useful than line-delimited messages. Sentinel terminators, especially newlines, are more error prone to generate and parse than a few bytes of length prefix followed by a message, repeat. In addition, t
|
2011-08-16
|
2011-10-04
|
13812
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
The EventSource garbage collection does not mention open/error events. It also does not seem to match the language entirely of WebSocket garbage collection.
|
2011-08-17
|
2011-10-04
|
13842
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
WONT
|
One issue that I have noticed is that there is no way to create an EventSource and attach event listeners to it before it connects to the server. This means that there is no way to ensure that no messages are missed between the creation of the EventSourc
|
2011-08-19
|
2011-08-19
|
13856
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
I am not sure whether it is due to the nature of this documentation but it would be very helpful to include an example of HTTP response and how it should react to HTTP 3xx and 4xx.
|
2011-08-22
|
2011-10-04
|
14048
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
INVA
|
Suggestion of change in process for "dispatch the event" in Server-Sent Events
|
2011-09-06
|
2011-10-18
|
14094
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
EventSource: Add example of listening for and using an event type other than 'message'
|
2011-09-08
|
2011-10-06
|
14120
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
INVA
|
Current spec for EventSource close method doesn't defined behaviour when close called after 'onopen' or 'onmessage'. For example, Google Chrome, closes connection if 'close' called while 'open' event dispatching and Opera doen't close it.
|
2011-09-13
|
2011-09-19
|
14144
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
Adding link to resolve the URL
|
2011-09-13
|
2011-10-21
|
14331
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
EventSource can end up in the wrong state due to race conditions (see comment 12 paragraph 2)
|
2011-09-29
|
2011-10-27
|
14530
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
NEED
|
Hi, In Server-Sent Events Section "Processing model", it should be clearly stated how to avoid the pipelining of HTTP requests on the connection used for an event source. HTTP pipelining - decribed in RFC 2616 / section 8.1.2.2 - is the possibility for a
|
2011-10-21
|
2011-10-27
|
14592
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
EventSource should default to use "Use Credentials" set to false for CORS
|
2011-10-28
|
2011-10-31
|
14900
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
NEED
|
note about checking "origin" attribute of MessageEvent
|
2011-11-22
|
2012-07-25
|
15495
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
Update EventSource model to do automatic reconnect even in the face of network errors
|
2012-01-10
|
2012-10-10
|
15956
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
Mistype: HTTP 305 Use Proxy, HTTP 401 Unauthorized, and 407 Proxy Authentication Required should be treated transparently as for any other subresource. Should be: HTTP 305 Use Proxy, HTTP 401 Unauthorized, and HTTP 407 Proxy Authentication Required should
|
2012-02-11
|
2012-02-11
|
16070
|
WebAppsW
|
HISTORIC
|
contributor
|
RESO
|
FIXE
|
uses MessageEvent but doesn't define or reference external definition
|
2012-02-22
|
2014-12-04
|
16224
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
WONT
|
Change .readyState to use string values rather than numeric constants
|
2012-03-04
|
2012-03-13
|
16281
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
INVA
|
yt uyt iu tyu tyu
|
2012-03-09
|
2012-03-09
|
16866
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
EOF is no longer valid as newline so "and the end of the file being the four ways in which a line can end" should be removed.
|
2012-04-26
|
2012-07-10
|
17266
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
INVA
|
You don't have permission to access /trouves on this server.
|
2012-05-31
|
2012-05-31
|
18320
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
DUPL
|
Clarify how reconnection works after losing internet connectivity
|
2012-07-18
|
2012-08-07
|
18653
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
wrong bug tracker link
|
2012-08-22
|
2012-10-19
|
18796
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
INVA
|
HTTP 204 not specified
|
2012-09-06
|
2012-10-11
|
22958
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
INVA
|
"The parameter's value must be 'utf-8'"
|
2013-08-14
|
2013-09-13
|
22997
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
FIXE
|
Better to have a clear statement: firing error or not, if Event streams doesn't encode as UTF-8 format.
|
2013-08-18
|
2013-09-12
|
28823
|
WebAppsW
|
HISTORIC
|
ian
|
RESO
|
MOVE
|
Course of action even after Event Source retry failure.
|
2015-06-17
|
2015-10-05
|