CloudServices/Notifications/Meetings/2011-01-18

First Iteration Meeting

Goals for next week:

• Demo - Three computers: Two clients, one web app.
  • Allow notifications from a web app using extension-created dialog
  • Notifications should appear immediately on both clients once web app pushes notification
  • Disable (revoke) notifications for particular app

Todos:

• General
  • Set up user repositories
  • Use a richer JSON format ("type": "…", "id": "…", "app": "token", "timestamp": "…", "payload": "…"})
• Server-side:
  • Change how server handles multiple connections
  • Get grant and revoke API for "mailbox tokens" working
• Client-side:
  • User is asked to receive notifications. The domain name of the site is displayed.
  • Browser makes token and hands it out to the user through callback.
  • Browser will also register the user, the app and the token with the server
  • Every Notification will display the domain name of where it's coming from
  • XUL code allowing for a preference window displaying all accepted domain names. User can delete notifications from there. (server will reflect this)
  • long polling approach revisited.

Granting approach change

• User is asked to receive notifications.

Discussion Points:

• Q: How do we handle spoofing?
  • A: We don't. Display a dialog with domain included "GMail (mail.google.com) wants to send you notifications. Allow?"
• Q: Should we use a doorbell mechanism?
  • A: No. Involves a lot of overhead; FeedURL (persistence especially) would be difficult to implement by clients. "Joe's Bakery just wants to push a button and send notifications, not build its own feed mechanism"

Upcoming meetings to be scheduled with:

• UX
• bsmith (crypto)
• rnewman (Queuing systems)