- Added Multipart/files support
- Solves #29
- Reconnect headers are now async. You can use async functions to fetch new headers, but make sure to return a
Map<String, String>
from the function. - Refer README example for more info.
- Reconnect headers are now async. You can use async functions to fetch new headers, but make sure to return a
- Solves #25
- The
onError
method now includes the JSON response from the backend in the error message, if the backend sends a JSON response to the frontend.
- The
- Added
reconnectHeaders
parameter inReconnectConfig
class.- If you want to send custom headers during reconnect which are different from the initial connection, you can use this parameter.
- If you don't want to send any headers, you can skip this, initial headers will be used.
- Refer README example for more info
- Added Http Client Adapter to allow usage of different http clients
- Thanks to jcarvalho-ptech for the PR
- Updated Http package version to
1.2.2
- Solves #18
- Ensures continuous connection even when network availability changes. (Again, I know, I know 🥹)
- Thanks to Andrew Abegg for the PR
- Solves #19
- Fixed README.md file for the example code.
- Solves #18
- Ensures continuous connection even when network availability changes.
- Added
ReconnectConfig
class to manage reconnection settings.- Closes #7
- If you are using
autoReconnect
parameter inconnect
method,reconnectConfig
param is required. - Now you can set backoff strategy, max retries and retry interval.
- Check the updated README for more info.
- Solves #12
- Disposing the instance of stream when
disconnect
method is called.
- Disposing the instance of stream when
- Solves #13
onSuccessCallback
should not be called unless 200 is returned- Thanks to Jan Gruenwaldt for the PR
- Solves #11
onError
method not getting triggered for non 200 status codes.
- Updated Http package version to
1.2.1
- Disabled web support due to dependancy issue.
- Refer #5 for more info.
- Web support #5
- Your existing code now flawlessly extends its magic to the web – no extra setup required, just pure, uninterrupted functionality across platforms!
- Readme's
EventFlux for Every Scenario
Section
spwan
method- Solves #3
- Provides users the flexibility to implement multiple SSE connections.
- See the "Supercharged" section in the README for usage instructions.
- Solves #2
- Retry doesn't use provided headers.
- If the connection is intentionaly severed/disconnected by calling
disconnet()
method, then theautoReconnect
will not try to reconnect the connection again and again.- I know, it's dumb mistake I made. Sorry. 🥹
- Updated the
connect
method to be a void function instead of returningEventFluxResponse
. This change accompanies the introduction of theonSuccessCallback
parameter, which provides theEventFluxResponse
via callback. This modification simplifies the connection process, making reconnections and stream updates more predictable and manageable.
- support for
autoReconnect
on connect method.
- Core functionality for connecting to server-sent event streams.
EventFlux
class to manage event stream connections.EventFluxData
class for representing event data.EventFluxException
class for handling exceptions.- Support for both GET and POST connection types.
- Error and Disconnect handling and reconnection logic.
Hello world