Please consider creating a web browser service worker SignalR client example.

[davidfowl]

[rdepena]

+1

[illeb]

+1 Any news on this?

[unsafecode]

+1

[bradygaster]

Will get on this.

[gerfen]

+1 thanks!

[etaxi341]

Totally need this... Any news?

[bradygaster]

@etaxi341 no progress has been made on the sample yet, but the support exists. @anurse do you suppose there'd be any issues putting this together? any known issues trying to pair SignalR with web browser service workers we've already seen? Cursory looks at the docs on service workers - feels like a slightly different paradigm that presumes the potential for "disconnectedness." That would thwart SignalR inherently, it would seem. that said, i'd be interested in what sort of scenarios you'd like to see, @etaxi341?

[davidfowl]

We added support for this in 3.0.

[bradygaster]

i've not seen a sample for this yet, will review the docs and see if something's complete enough, unless you have a gist sitting around? :)

[davidfowl]

https://github.com/aspnet/AspNetCore/blob/9158039c9515e46d39c90f462ae91827769889c4/src/SignalR/samples/SignalRSamples/wwwroot/worker.html

https://github.com/aspnet/AspNetCore/blob/9158039c9515e46d39c90f462ae91827769889c4/src/SignalR/samples/SignalRSamples/wwwroot/worker.js

[etaxi341]

These are sadly not Service Worker examples. This is a Web Worker :/
I would just want to know if it's possible to call a push event of the service worker via SignalR, so I don't have to rewrite my whole chat system.

[davidfowl]

Service workers aren’t the place for persistent connections.