gecko/services/notifications
Kyle Huey 45adfbf2c8 Bug 798491: Add an option to stick all chrome JSMs/JS components in the same compartment. r=mrbkap,philikon
--HG--
extra : rebase_source : 98337b6a8c07d05e8c961a452dd05a7d75c3c60b
2012-10-31 09:13:28 -07:00
..
tests Bug 774032 bonus - Use @DEPTH@ and @relativesrcdir@ in Makefile.in. r=ted 2012-08-04 20:26:44 +02:00
Makefile.in Bug 781307 - Remove rules from services/ Makefile.in's; r=glandium 2012-08-09 13:12:29 -07:00
NotificationsComponents.manifest Bug 754062 - Add skeleton for browser notifications service; r=gps 2012-06-22 09:24:39 -07:00
README Bug 754062 - Add skeleton for browser notifications service; r=gps 2012-06-22 09:24:39 -07:00
service.js Bug 798491: Add an option to stick all chrome JSMs/JS components in the same compartment. r=mrbkap,philikon 2012-10-31 09:13:28 -07:00
services-notifications.js Bug 754062 - Add skeleton for browser notifications service; r=gps 2012-06-22 09:24:39 -07:00

Here lies most of the moving parts for push notifcations in the browser. DOM
and UI bindings will live elsewhere; these files deal with talking to the API,
storing messages, and creating persistent connections to the notification
server.

Structure:

services.js::Service
  This is a singleton that manages API calls and message storage. It's an
  instance of the NotificationSvc class. Messages and state are persisted to a
  JSON file on disk.