Marc Gravell

The typical usage would be to subclass WebSocketsMessageProcessor; this then allows you to override various methods, including methods that relate to each WebSocketConnection (as a parameter), such as: OnOpened OnAuthenticate...

nice; awesome stuff On 2 March 2016 at 07:46, pjanning [email protected] wrote: > @rherwig https://github.com/rherwig and me built a little example with > NetGain. Here are our Repositories: > >...

In a perfect world, we'd probably make use of it, but basically we considered: - wss is awkward to implement from the technical perspective, especially if you are working from...

@pjanning To expand on that, @NickCraver has reminded me that we _do use wss_, but: not at the library level. We terminate that at the NLB (haproxy). The library does...

Good question. It isn't a design feature right now. We use haproxy to terminate SSL before the web-socket server. We are interested in playing with the TLS work that @drawaes...

So are we :) On Sun, 15 Apr 2018, 03:24 Terry Phillips, wrote: > Ah, ok. I am on windows server so that may be a bit hard. Thanks for...

Or rather, we use both. On Sun, 15 Apr 2018, 08:20 Marc Gravell, wrote: > So are we :) > > On Sun, 15 Apr 2018, 03:24 Terry Phillips, >...

I don't have a roadmap / schedule for it, but yes that is a long term aim; however, I suspect this will require pretty much a rewrite of the socket...

Re streams: it should be pretty trivial to write an extension method (or regular utility method) that loops a buffer over a stream; we could add it as an API,...

We discussed this in a parallel issue, but basically it isn't on my list of things to do. Reasons: 1. Since the library builds on the socket API (not the...