Scarlet icon indicating copy to clipboard operation
Scarlet copied to clipboard

A Retrofit inspired WebSocket client for Kotlin, Java, and Android

Results 107 Scarlet issues
Sort by recently updated
recently updated
newest added

While investigating an issue with our Socket Connection I noticed that Scarlets' [SocketIoClient](https://github.com/Tinder/Scarlet/blob/0.2.x/scarlet-protocol-socketio-client/src/main/java/com/tinder/scarlet/socketio/client/SocketIoClient.kt) has a problem when we are trying to reconnect after the Server triggered a disconnect. To go...

If we setup Scarlet with lifecycleOwner from Activity or Fragment then when onDestroy them Lifecycle's Scarlet will still retry again. ``` val configuration = Scarlet.Configuration( lifecycle = AndroidLifecycle.ofLifecycleOwnerForeground(application, **this**), messageAdapterFactories...

This will resolve #78 I'm not sure if this is the best way to write the headers implementation but I will be happy to hear any suggestions.

I've got multiple methods annotated with @ Receive inside Scarlet's interface. The problem is that, for example, when a Route is sent on the socket from the server, all 4...

The standard for websocket communication is often regarded as being [STOMP](http://stomp.github.io/). Does this / will this library have STOMP compatibility in its message layer?

I'm trying to emulate socket.emit with this library and I'm not really sure how to do that? Is communicating with a SocketIO server supported?

Why should we add this line when we want to create a scarlet object?? When i remove this Koin cant inject the object !!

I am trying to build an app which should connect via WebSocket to a server at runtime (the user will be prompt to give the address of the server and...

Hello, I'm struggling to write some unit tests to validate my scarlet integration into an android app. The scarlet-test-utils seems pretty useful, but its usage is a bit ... obscure...

enhancement
help wanted

I'm dealing with a problem that my server could be unstable at the time and he could silently reboot itself. The issue is that my socket is not retrying connection...