reflex-websocket-interface icon indicating copy to clipboard operation
reflex-websocket-interface copied to clipboard

A simple to use interface for websocket using reflex-frp

Results 3 reflex-websocket-interface issues
Sort by recently updated
recently updated
newest added

For deeply nested requests there is a lot of overhead with ToJSON/FromJSON instances `{"tag":"Recurse","contents":{"tag":"Recurse","contents":{"tag":"Recurse","contents":{"tag":"Recurse","contents":{"tag":"Recurse","contents":{"tag":"Recurse","contents":{"tag":"Recurse","contents":{"tag":"Recurse","contents":{"tag":"Recurse","contents":{"tag":"Terminal","contents":["SomeType",[],null]}}}}}}}}}}]` Also a better Show instance will be useful in debugging

servant-reflex has the notion of a "tag" (not to be confused with tagging Events, etc.) where an XHR request can be "tagged" with some meta information that will be given...

Is it possible to use your library and have the server push content down to the client, unrequested? Or perhaps the client could make a request and the server could...