David Luecke

How would I reproduce your issue?

From what I could see, it does not seem as if Express will support HTTP2 any time soon so this will be very dependent on #258.

Yes, connections will trigger a `disconnect` event and removed from all channels automatically upon token expiry (see https://github.com/feathersjs/feathers/blob/dove/packages/authentication/src/jwt.ts#L46) and no longer receive real-time updates. It would be the client's responsibility...

Correct. If you intentionally have shorter token expiries while the client doesn't do anything (when the token is expired and they try to make a request it'll throw an error...

This was a good question. I've been thinking about ways for the server to let the client know that their connection has expired but I can't think of a good...

Indeed, an MQTT transport has been on the radar for a while. Many parts that would be relevant for creating a transport are documented: - [Configure functions](https://docs.feathersjs.com/guides/basics/generator.html#configure-functions) to create a...

What I meant is that the acknowledgement has to be able to actually send back custom data not just an `ok` status. Two separate channels linked by a unique identifier...

I'm doing some v5 rework at the moment so this would be perfect timing since I'd also like to look at a native websocket transport which I believe has similar...

I agree on the type coercion - it's mainly intended for query schemas since they generally come in as strings for REST calls. Not sure what the best setup would...

Thanks for digging into this! Looks like that part of the code is causing a couple of problems (like the one I've been trying to fix in #1889). What the...