@Sam You can call ServiceStack Services via the Service Gateway (https://docs.servicestack.net/service-gateway) the same non ServiceStack Services:

var response = HostContext,AppHost.GetServiceGateway().Send(new MyRequest());

You would need to use SignalR's client to use SignalR. The C# ServiceClients are only for calling ServiceStack Services, likewise the C# ServerEventsClient is for consuming ServiceStack's Server Events.

Now that SignalR has officially release, https://docs.microsoft.com/en-us/aspnet/core/signalr/introduction?view=aspnetcore-2.2

Do you plan on adding some examples and/or documentation on how to best integrate it into service stack. It would be awesome if the jsonclient got support for it with the backend.

Is there a working implementation for this yet? I am running into a lot of problems ("user ID required", routing issues etc..) when combining SignalR and ServiceStack in .NET core.

The integrated ServiceStack solution for real-time events is to use Server Events.

But if preferred you can happily configure SignalR in the same .NET Core App as ServiceStack, neither framework has dependencies or knowledge of each other but they both have access to the same dependencies registered in .NET Core's IServiceCollection.

Out of curiosity is there any movement on this?

This is awesome news ! Luv the idea that Rest api , signalr and server sent events can be fully integrated in SS. What will be absolutely awesome is Rest , SignalR , SSE and Akka.net
That will put SS on a different planet ;)

Note that authenticated SSE isn't supported in IE9 and earlier browsers. In other browsers that don't support XmlHttpRequest to send http cookies and/or custom headers it cannot be implemented either.
Sadly to say, for this reason we are forced to leave SSE toward SignalR.

We're using SignalR and we're seriously considering moving to ServiceStack for our api v2. But we'd like to keep using signalr for some operations, and here's why:
Server Sent Events are virtually unusable if you're serving content to iOS-devices. iOS only allows a small number of concurrent connections to any server, and an SSE endpoint blocks one of those connections, resulting in other requests not being allowed through. WebSockets doesn't cause this, on the other hand.

I've completed an initial typed C# client implementation at https://github.com/jklemmack/ServerSentEvents4ServiceStack. This repo also has a lighter-weight server implementation, where the "data" elements are raw DTOs, and the "event" field is used to govern the categorization of messages.

Apologies, I meant just SS's JS client bindings. The C# libraries have yet to be developed, I'll look at providing some integration with C# soon.

you mention in your comment that the SSE integration extends to the client libraries - how is this accessible, Demis? I can only see info for javascript clients....

Any plans on a JsonServiceClient-based C# EventSource client?