Diego Esmerio

The client process the websocket messages as they come. The websocket protocol guarantees the order of the messages, but maybe a big message might be deserialized slower than the next...

I was thinking about changing the serializer to the same as Fable.Remoting as it seems to be working ok for the same use case. I hope the bundle size won't...

I uploaded a version using the same serializer as Remoting with a small tweak that check the base server union type and auto register every type used inside it if...

I added a crude custom serializer support on the `pre2` version. The support now is just for the messages the client sends and the server receives. As the server only...

There is no communication agreement between server and client, that should be possible but not sure if it could be friendly. There is a way to do custom communication on...

It's a little experimental, but can you test the package [Elmish.Bridge.DotNetClient](https://www.nuget.org/packages/Elmish.Bridge.DotNetClient)? The Fable one only works in the browser, but this one should work for desktop apps.

Hi, thanks for using it! About the use case, how different is it from having the server sending a message to the client on its `init` function? That should behave...

I'm not sure if I understand it completely... Would it be the same as the following? Today: - Client sends `GiveMeValueA` - Server receives `GiveMeValueA` and responds with `HaveTheValue (Some...

I might have now the knowledge I was missing to implement this feature. I hope to have some fruitful experiments soon!

@0x53A I added a method `AskClient` on the `ServerHub` as an experiment on the version [5.0.0-rc-4](https://www.nuget.org/packages/Elmish.Bridge.Client/5.0.0-rc-4). Are you still interested in testing it? Also, I'm not sure what to do...