On 08/06/2015 03:05 PM, John Mazzitelli wrote:
> Is there something you'd require that I might be missing?
If we have something like this:
> So, we are likely going to follow the route of implementing a "check" on
each
> onMessage. Not clean, certainly invasive, but works. I'll try to
> alleviate the pain as much as I can by providing simple APIs.
then that would be very helpful and possibly most of what we need (I say "most"
because this wouldn't cover the use-case Heiko just mentioned - what if a user has
been removed from the system - we would need to know that and forcibly disconnect the
WebSocket connection - but that's an edge case. For now, just care about the general
use-case of a user making a connection - how do we authenticate that user?)
I'd say that it even fulfills this case, as the check would be done on
Accounts, having access to the session. Accounts would then close the
session if needed.
- Juca.