OAuth token invalidation

[David Albrecht <da...@wishery.com>]

All,

I've been reading the code to the project but can't figure this out. How
does an OAuth-protected resource signal to the container (Shindig) that
OAuth validation failed, and that the container needs to get a new token?

I've started issuing HTTP 401s from my service which seems to put Shindig
back into the "no token" state, but occasionally I get false positives
where it reverts from the "token" to "no token", too. I don't know why this
is happening, but it's annoying for our users and I'd like to fix it.

Thanks,
David R. Albrecht
Wishery