web: '>=0.5.0 <2.0.0'
.package:js
.3.3.0
.package:web
.dart2wasm
.3.2.0
.fetch
requests instead of XHR
requests.debugKey
parameter to SseClient
to include in logging.package:js
.2.16.0
.keepAlive
logic to SocketException
s.package:pedantic
to package:lints
repository
field.onConnected
with an error if the SseClient
receives an error before the connection is successfully opened.SseConnection
stream would result in an error.onConnected
to replace onOpen
.done
event to the connection sink
.onOpen
getter. Messages will now be buffered until a connection is established.package:uuid
.** Note ** This is not modelled as a breaking change as the server can handle messages from older clients. However, clients should be using the latest server if they require order guarantees.
shutdown
methods on SseHandler
and SseConnection
to allow closing connections immediately, ignoring any keep-alive periods.onClose
from SseConnection
and ensure the corresponding sink.close
correctly fires.onClose
event to the SseConnection
. This allows consumers to listen to this event in lue of sseConnection.sink.done
as that is not guaranteed to fire.keepAlive
may cause state errors when attempting to send messages on a closed stream.keepAlive
would only allow a single reconnection.isInKeepAlivePeriod
flag on SseConnection
. This flag will be true
when a connection has been dropped and is in the keep-alive period waiting for a client to reconnect.SseClient
would not send a done
event when there was an error with the SSE connection.isInKeepAlive
on SseConnection
private.Note that this is a breaking change but in actuality no one should be depending on this API.
keepAlive
parameter to the SseHandler
. If keepAlive
is supplied, the connection will remain active for this period after a disconnect and can be reconnected transparently. If there is no reconnect within that period, the connection will be closed normally.Possible Breaking Change Error messages may now be delayed up to 5 seconds in the client.
package:http
dependency.package:stream_channel
.>=2.1.0 <3.0.0
.package:uuid
version 2.0.close
and onClose
on an SseConnection
. This is simply handled by the underlying stream
/ sink
.SseConnection
were not properly closed.