NaikSoftware
No way to catch StompMessages which don't have a destination
Not able to response to non-destination commands coming from STOMP and thus not able to response to anything other than subscribed topics. Not able to extend anything from this library as well. So pretty much limited library.
Would be great to add a global "subscriber" to catch ANYTHING coming from stomp.
Hence people are starting to create implementations based on bad practices. https://github.com/NaikSoftware/StompProtocolAndroid/issues/18 (last comment)
I did a small gist with my own ported code from iOS: https://gist.github.com/heyarny/d6763eefef89da1d4eb69dd0d8263500
Use it as you like. It's easy, simple & extendable.
Uhhh, non-topic subscriptions are not part of the STOMP protocol. I'm not really sure why you'd want that, anyways.
But in terms of making the library more flexible, I agree with you, it would be good.
@forresthopkinsa I guess you didn't get it right. I mentioned "subscriptions" in term of this library, not STOMP. Since you also "subscribe" to lifecycle events with this library.
mStompClient.lifecycle().subscribe(lifecycleEvent -> {
switch (lifecycleEvent.getType()) {
...
I see what you mean. Yeah, that's a good point. Could you make an issue here detailing a little bit more what you're thinking, and I'll add it to the roadmap.
This project might end up implementing what you're suggesting, but it's generally in a pretty mature stage and it doesn't normally make big changes. But the downstream is in a less mature stage and can more easily make those changes.