[Cyberduck-trac] [Cyberduck] #2876: Cloud Files authentication re-use

[Cyberduck]

#2876: Cloud Files authentication re-use
-----------------------------+----------------------------------------------
 Reporter:  ej@…             |       Owner:  dkocher                
     Type:  enhancement      |      Status:  new                    
 Priority:  normal           |   Milestone:                         
Component:  cloudfiles       |     Version:  3.1.1                  
 Severity:  normal           |    Keywords:  cloudfiles optimization
-----------------------------+----------------------------------------------
 Optimization tip:  When the Log Drawer is open, I can see the HTTP
 request/response headers (thanks for that!).  What I've noticed is that
 unnecessary authentication calls are being repeated.  This may be an
 artifact of the application's internals and multiple connections, but
 Cyberduck only needs to authenticate once.  The X-Auth-Token returned by a
 successful authentication can be used for each connection to the storage
 or CDN systems.  Also, the URLs to the storage and CDN systems do not
 change between requests, so that information can be cached and re-used
 between each connection.

 So what I expected to see in the Log Drawer was one connection to
 https://api.mosso.com/auth with appropriate headers.  The response's X
 -Auth-Token, X-Storage-Url, and X-CDN-Management-Url can be cached and re-
 used for each subsequent connection.

 Be warned that the token will expire over time (possibly as short as an
 hour).  The application should trap a 401 (Unauthorized) response on a
 given request (to either storage or cdn system) and then re-authenticate
 to obtain an updated token.

 If you have any follow-up questions/comments, feel free to stop by
 freenode.net #cloudfiles.  We're not always "alive", but we'll answer when
 we wake up.

-- 
Ticket URL: <http://trac.cyberduck.ch/ticket/2876>
Cyberduck <http://cyberduck.ch>
FTP, SFTP, WebDAV and Amazon S3 Browser for Mac OS X.