Skip to content

Laurence Evans

My feedback

1 result found

  1. 71 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Laurence Evans supported this idea  · 
    An error occurred while saving the comment
    Laurence Evans commented  · 

    @Kunjan, SignalR and websocket support are different things. SignalR is primarily built for small message, distributed comms while websocket is a full-duplex tcp-based protocol without any such restrictions.

    2 issues I've run into myself when trying to use signalr to do some out of the ordinary use case stuff.
    https://github.com/SignalR/SignalR/issues/1114
    https://github.com/SignalR/SignalR/issues/1205

    Doing the same (sending an image) over websocket (XSockets implementation) was trivial and had no such issues.

    If ServiceStack had websocket support that'd be pretty awesome, it would allow for the creation of duplex comms in a somewhat standardised manner.

Feedback and Knowledge Base