Hi, I'm working on a project that require connect to twitter service. The reason I have to do this is that we want to use a twitter account to regularly grab the newest twits about certain topic term. But there is a rate limit to this function. So, we would like to use client's account to access twitter. This would hopefully increase the rate limit. I already have passport doing normal twitter/google/local strategy. I want to separate the "connect to twitter" from the normal login. My initial idea is to create a temp variable holder for current req.user, then let client login as twitter, then I swap back the original account to their current session and create in mongo an entry linking the login account with their twitter account. But this cause a problem as the variable in server side will mess up the user when another user is trying to connect at the same time and handled by the same server instance. (I also have cluster)
The reasonable method I think is to put the original account info in the req, then retrieve it when user authenticated and swap back. But I would like to know how this feature is usually done? Is there exsiting node modules that can do this? I checked passport and a few other oauth based sign in system, they are all for initial login, not for connecting to a service. Thanks. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
