Noam Ben Ari

@dirty-hippie I'm not maintaining it, but it has a new maintainer - @kirs , so no, it is actually more active than it has been in a long while... :)

Yes, it's been asked for a few times. Since v0.7.0 is nearly done, it is set for v0.8.0. The issue will stay here until it's done. Thanks.

Hi, I'm not getting to it... I was thinking about an API like this: require_login :token_allowed => true, :only => [:json] This way it extends require_login to allow or disallow...

Actually require_login has all the options of a before filter, so I shouldn't touch 'only'. Maybe another before filter, allows_token_authentication. Not sure. How is it done in other gems?

I'm thinking this design: 1. on password creation/update create another field - auth_token 2. a new before_filter - 'allow_token_authentication' needs to be placed in the controller (along with options like...

The way http-kit does it, without re-implementing any middleware, is to stop function execution at the innermost function (your own handler), and only when the response is processed and ready,...

You're right, about http-kit - if it's a websocket connection, it just sends a 100 response back which passes the middleware fine. After that the connection is upgraded so no...