Open blazing-gig opened 1 year ago
This isn't in my short term roadmap, but I may look into it in the future.
@miguelgrinberg Thanks for responding. I understand and it's a little unfortunate. Is there any way I could help to get it expedited ? Reason being I'm looking to build a solution that depends on at least once message delivery semantics without having to go through the jazz of event acks, maintaining offset state etc.,
Also, if you could make your roadmap publicly available on Github, it would help folks using the library plan better in terms of functionality/features they can expect in the near future.
Please let me know your thoughts on the same. Thanks!
The reason this does not rank high on my list is that it has never been a big issue for me. But if you would like to build something out yourself I would be glad to consider it for inclusion.
If one day this becomes my job, then I would be glad to maintain a publicly available roadmap and provide information on what features will be released when. Right now the financial support I get from my work on this project is small, so I can only work on this on my free time, and cannot provide any commitments as to the time or content of future releases.
Is your feature request related to a problem? Please describe. I recently saw here that connection state recovery has been implemented in the JS version of socket.io. Was wondering if and when it could be implemented here as well including supporting adapters such as Redis streams, PostgreSQL etc.,
Btw, kudos for all the great work that's been put into this library until now and the time to come!