Add method and content options

[shimaore]

This allows for example to support the POST method of CouchDB

[piranna]

Are they in the spec? Can you point us to it?

[shimaore]

As far as I can tell, these would be extensions, just like the headers extension.

[shimaore]

To be explicit: the spec doesn't specify which method is used to request the event stream, so any method that returns text/event-stream would be valid in terms of the protocol.

However the API / interface does not seem to allow anything besides GET.

[piranna]

GET is the default one, so if it's not specified, then it will be GET only.

[aslakhellesoy]

Why would you want to use an EventSource client to issue POST requests? It doesn't look like the CouchDB doc you linked to suggests using EventSource for anything else than consuming server-sent events. The POST part of the API should be used with a standard (non-EventSource) HTTP request (using a http client library such as fetch).

[shimaore]

@aslakhellesoy The eventsource feed is data returned by the server, regardless of the method used to request it, the same way that you can get an HTML or a JSON response whether you use GET or POST to request it. In this specific case a selector-type request can only be submitted by using POST, and it will return an event-source stream if requested to do so.

@piranna I understand your viewpoint, thank you for your feedback!