This project is read-only. 1.2 compatibility

Nov 24, 2014 at 3:57 PM

We have a websocket based application that runs both in the various browsers as well as mobile Xamarin based apps on iOS and Android. We have just upgraded the library from 0.9.16 -> 1.1 -> 1.2 to benefit from amongst others the binary support.

Now as expected this kind of broke the application in the native implementations, and while we have been tinkering around with this (still in a development branch, we have not really go to actually diving into this issue until now). Thus to the reason for my posting, while I know this is mainly .NET based and node.js is possibly not the first websocket backend server chosen for most projects here, I would like to ask if anyone here have experience going through a similar migration using Websocket4Net against a 1.2 based backend.

Thank you in advance

Kenneth Thorman