You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2021. It is now read-only.
Java client seems to be having issues with newer versions of Java-Websocket with latest commit to 28 Nov 2017. I am very much interested in future of this repository.
The text was updated successfully, but these errors were encountered:
Hey @yasserf, I guess you're busy with other stuff and this is "just an open source project". But assuming you work for deepstream.io, can you tell us what's the general strategy about this Java client? Isn't it important for the company to have a stable, up-to-date Java/Android client?!? I mean this is such a cool project and looking at the number of Java and Android devices out there, it just doesn't make sense to me that deepstream.io isn't investing a bit more here. At least fixing critical issues... Any insights would be very welcome. Thank you.
@yasserf I will open a PR someday, not sure when. I have already invested enough time in understanding this project and making it work in our project. I'm myself too busy with work as well as personal project. I will open a PR as soon as I get time to make proper fixes. Thank You.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Java client seems to be having issues with newer versions of Java-Websocket with latest commit to 28 Nov 2017. I am very much interested in future of this repository.
The text was updated successfully, but these errors were encountered: