[Notification] Do not keep separated copy of notifications
authorCaio Marcelo de Oliveira Filho <caio.oliveira@intel.com>
Mon, 23 Sep 2013 17:18:12 +0000 (14:18 -0300)
committerCaio Marcelo de Oliveira Filho <caio.oliveira@intel.com>
Thu, 26 Sep 2013 12:36:01 +0000 (09:36 -0300)
commite2e502fce377206eded9ff137d2e6f227bfb572d
tree332a63b35e219fddb61987f9d3f2353881eacaf5
parent3d6a5ace6dff85d07b901b377f14e15f95ac2198
[Notification] Do not keep separated copy of notifications

Notification object is essentialy as a "property bag" to be used in
conjunction with tizen.notification.* functions. Now that we have
v8tools.forceSetProperty() we can keep certain properties read-only and
do not need to worry about user changing the notification, so no need to
keep our own copy of the data.

Note that since Notification API doesn't rely on GC to identify
notifications that should be removed, one needs to explicitly call the
remove function, or wait for user removal via the UI.
notification/notification_api.js