[Bps-public-commit] jifty-plugin-authentication-twitter branch, master, updated. f67e29623021e466d490bba1362154cd4cab8cd8

[Shawn Moore]

The branch, master has been updated
       via  f67e29623021e466d490bba1362154cd4cab8cd8 (commit)
      from  8854bfdbc8aad34516db04ded57c72a5a0534e77 (commit)

Summary of changes:
 .../Plugin/Authentication/Twitter/Dispatcher.pm    |   16 ++++++++++++++++
 1 files changed, 16 insertions(+), 0 deletions(-)

- Log -----------------------------------------------------------------
commit f67e29623021e466d490bba1362154cd4cab8cd8
Author: Shawn M Moore <sartak at bestpractical.com>
Date:   Fri Jun 11 12:50:20 2010 -0400

    Doc for the two URLs

diff --git a/lib/Jifty/Plugin/Authentication/Twitter/Dispatcher.pm b/lib/Jifty/Plugin/Authentication/Twitter/Dispatcher.pm
index d789148..589f067 100644
--- a/lib/Jifty/Plugin/Authentication/Twitter/Dispatcher.pm
+++ b/lib/Jifty/Plugin/Authentication/Twitter/Dispatcher.pm
@@ -20,6 +20,11 @@ Jifty::Plugin::Authentication::Twitter::Dispatcher - dispatcher for Twitter plug
 
 All the dispatcher rules jifty needs to support L<Jifty::Authentication::Twitter>
 
+=head2 /twitter/login
+
+Talk to Twitter to get a request token, then redirect the user to Twitter so
+they can authorize it.
+
 =cut
 
 on '/twitter/login' => run {
@@ -70,6 +75,17 @@ on '/twitter/login' => run {
     Jifty::Dispatcher::_abort();
 };
 
+=head2 /twitter/callback
+
+Twitter redirects the user back here after they've authorized the request
+token. We have to talk to Twitter again to trade the request token for an
+access token, at which point Twitter also tells us which Twitter account the
+user is logged into.
+
+If all goes well we load or create the user's account.
+
+=cut
+
 on '/twitter/callback' => run {
     my ($plugin) = Jifty->find_plugin('Jifty::Plugin::Authentication::Twitter');
     my $request_token = Jifty->web->request->argument('oauth_token');

-----------------------------------------------------------------------