Accessing social networking Web sites through OAuth, Part 3, Deploy the Web Twitter client to Google App Engine
From the developerWorks archives
Date archived: January 4, 2017 | First published: April 13, 2010
OAuth is an open protocol that lets users share their protected resources among different Web sites, without risking exposure of users' credentials. Part 1 of this series introduced OAuth and showed you how to develop an OAuth-enabled desktop Twitter client. In Part 2, you learned how to develop an OAuth-enabled Web Twitter client. In this final part of the series, you will deploy the Web application developed in Part 2 to the Google App Engine (GAE).
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.