eventflux 2.2.2-dev.2

Efficient handling of server-sent event streams with easy connectivity and data management.

Changelog 📝

v2.2.2-dev.2 🛠️

• Potential fix for multiple connection issue when using single instance method
  • Solves #32
• Added a check to ensure that stream is not closed before sending data

v2.2.1 🚀

• Added Multipart/files support
  • Now you can send multipart/files data to the server.
  • Thanks to Pedro for the PR
  • Refer README example for more info.

v2.2.0 🛠️

• 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.

v2.1.2 🛠️

• 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.

v2.1.1 🚀

• Added reconnectHeaders parameter in ReconnectConfig 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

v2.1.0 🛠️

• 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.

v2.0.1 🛠️

• Solves #18
  • Ensures continuous connection even when network availability changes.

v2.0.0 🚀

Breaking

• Added ReconnectConfig class to manage reconnection settings.
  • Closes #7
  • If you are using autoReconnect parameter in connect method, reconnectConfig param is required.
  • Now you can set backoff strategy, max retries and retry interval.
  • Check the updated README for more info.

1.7.0 🛠️

• Solves #12
  • Disposing the instance of stream when disconnect method is called.
• Solves #13
  • onSuccessCallback should not be called unless 200 is returned
  • Thanks to Jan Gruenwaldt for the PR

v1.6.9 🛠️

• Solves #11
  • onError method not getting triggered for non 200 status codes.

v1.6.7 🛠️

• Updated Http package version to 1.2.1

v1.6.6

Breaking

• Disabled web support due to dependancy issue.
  • Refer #5 for more info.

v1.6.0 🚀

Added

• Web support #5
  • Your existing code now flawlessly extends its magic to the web – no extra setup required, just pure, uninterrupted functionality across platforms!

v1.5.1 📝

Updated

• Readme's EventFlux for Every Scenario Section

v1.5.0 🚀

Added

• spwan method
  • Solves #3
  • Provides users the flexibility to implement multiple SSE connections.
  • See the "Supercharged" section in the README for usage instructions.

v1.0.1 🛠️

• Solves #2
  • Retry doesn't use provided headers.

v1.0.0+2 🛠️

• If the connection is intentionaly severed/disconnected by calling disconnet() method, then the autoReconnect will not try to reconnect the connection again and again.
  • I know, it's dumb mistake I made. Sorry. 🥹

v1.0.0 🚀

Breaking

• Updated the connect method to be a void function instead of returning EventFluxResponse. This change accompanies the introduction of the onSuccessCallback parameter, which provides the EventFluxResponse via callback. This modification simplifies the connection process, making reconnections and stream updates more predictable and manageable.

v0.6.2 🚀

Added

• support for autoReconnect on connect method.

v0.6.1 🚀

Added

• 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.

v0.0.1 🍼

• Hello world