Lab 5: App Engine storage and third party authentication

This lab is only for the TDDI15 course

In progress

Summary

In this lab, you will learn about Google App Engine (GAE) storage as well as using third party services for both user authentication as well as other features. You will extend your previous application to use a GAE object storage instead of a relational database and use a third party provider to handle your user authentication. For a higher grade (4 or 5) you will extend your project with more technologies.

Runtime environment

In the launch configuration of your GWT project, you must ensure that the Google App Engine is enabled. There is a checkbox for enabling/disabling the App Engine in Project Properties (use Project -> Properties -> Google -> App Engine check "Use Google App Engine")

Assignment

The assignment

For grade 3

Update your lab4 -miniproject to use GAE ORM instead of the sqlite/mysql-database. Also add user authentication using openID for your project.

For grade 4

The extra extensions for a grade 4 miniproject includes everything for grade 3 and a proof-of-concept implementation that uses at least one new api/framework beyond labs 1-4 (such as Blogger, Flicker, Twitter, or similar). We are looking on understanding of the api/framework not lost of code.

For grade 5

Everything for grade 4 and provide an API/Framework for other developers for you website,similar to one you might have used in lab 4 (Blogger, Flicker, Twitter). You should provide/expose at least three different functions that a third party developer can utilize using your API/Framework.