a:11:{s:9:"#provides";s:26:"dojo.data.api.Notification";s:9:"#resource";s:24:"data/api/Notification.js";s:9:"#requires";a:1:{i:0;a:2:{i:0;s:6:"common";i:1;s:18:"dojo.data.api.Read";}}s:26:"dojo.data.api.Notification";a:6:{s:4:"type";s:8:"Function";s:6:"chains";a:2:{s:9:"prototype";a:1:{i:0;s:18:"dojo.data.api.Read";}s:4:"call";a:1:{i:0;s:18:"dojo.data.api.Read";}}s:7:"summary";s:167:"This is an abstract API that data provider implementations conform to.
This file defines functions signatures and intentionally leaves all the
functions unimplemented.";s:11:"description";s:641:"This API defines a set of APIs that all datastores that conform to the
Notifications API must implement.  In general, most stores will implement
these APIs as no-op functions for users who wish to monitor them to be able
to connect to then via dojo.connect().  For non-users of dojo.connect,
they should be able to just replace the function on the store to obtain
notifications.  Both read-only and read-write stores may implement
this feature.  In the case of a read-only store, this feature makes sense if
the store itself does internal polling to a back-end server and periodically updates
its cache of items (deletes, adds, and updates).";s:8:"examples";a:1:{i:0;s:173:"

	function onSet(item, attribute, oldValue, newValue) {
		//Do something with the information...
	};
	var store = new some.newStore();
	dojo.connect(store, "onSet", onSet);";}s:9:"classlike";b:1;}s:38:"dojo.data.api.Notification.getFeatures";a:4:{s:9:"prototype";s:26:"dojo.data.api.Notification";s:4:"type";s:8:"Function";s:6:"source";s:84:"		return {
			'dojo.data.api.Read': true,
			'dojo.data.api.Notification': true
		};";s:7:"summary";s:36:"See dojo.data.api.Read.getFeatures()";}s:32:"dojo.data.api.Notification.onSet";a:7:{s:9:"prototype";s:26:"dojo.data.api.Notification";s:4:"type";s:8:"Function";s:10:"parameters";a:4:{s:4:"item";a:2:{s:4:"type";s:4:"item";s:7:"summary";s:24:"The item being modified.";}s:9:"attribute";a:2:{s:4:"type";s:21:"attribute-name-string";s:7:"summary";s:57:"The attribute being changed represented as a string name.";}s:8:"oldValue";a:2:{s:4:"type";s:14:"object | array";s:7:"summary";s:257:"The old value of the attribute.  In the case of single value calls, such as setValue, unsetAttribute, etc,
this value will be generally be an atomic value of some sort (string, int, etc, object).  In the case of
multi-valued attributes, it will be an array.";}s:8:"newValue";a:2:{s:4:"type";s:14:"object | array";s:7:"summary";s:303:"The new value of the attribute.  In the case of single value calls, such as setValue, this value will be
generally be an atomic value of some sort (string, int, etc, object).  In the case of multi-valued attributes,
it will be an array.  In the case of unsetAttribute, the new value will be 'undefined'.";}}s:6:"source";s:73:"		throw new Error('Unimplemented API: dojo.data.api.Notification.onSet');";s:7:"summary";s:98:"This function is called any time an item is modified via setValue, setValues, unsetAttribute, etc.";s:11:"description";s:346:"This function is called any time an item is modified via setValue, setValues, unsetAttribute, etc.
Its purpose is to provide a hook point for those who wish to monitor actions on items in the store
in a simple manner.  The general expected usage is to dojo.connect() to the store's
implementation and be called after the store function is called.";s:14:"return_summary";s:8:"Nothing.";}s:32:"dojo.data.api.Notification.onNew";a:7:{s:9:"prototype";s:26:"dojo.data.api.Notification";s:4:"type";s:8:"Function";s:10:"parameters";a:2:{s:7:"newItem";a:2:{s:4:"type";s:4:"item";s:7:"summary";s:17:"The item created.";}s:10:"parentInfo";a:3:{s:8:"optional";b:1;s:4:"type";s:6:"object";s:7:"summary";s:1118:"An optional javascript object that is passed when the item created was placed in the store
hierarchy as a value f another item's attribute, instead of a root level item.  Note that if this
function is invoked with a value for parentInfo, then onSet is not invoked stating the attribute of
the parent item was modified.  This is to avoid getting two notification  events occurring when a new item
with a parent is created.  The structure passed in is as follows:
{
item: someItem,							//The parent item
attribute:	"attribute-name-string",	//The attribute the new item was assigned to.
oldValue: something	//Whatever was the previous value for the attribute.
//If it is a single-value attribute only, then this value will be a single value.
//If it was a multi-valued attribute, then this will be an array of all the values minues the new one.
newValue: something	//The new value of the attribute.  In the case of single value calls, such as setValue, this value will be
//generally be an atomic value of some sort (string, int, etc, object).  In the case of multi-valued attributes,
//it will be an array.
}";}}s:6:"source";s:73:"		throw new Error('Unimplemented API: dojo.data.api.Notification.onNew');";s:7:"summary";s:143:"This function is called any time a new item is created in the store.
It is called immediately after the store newItem processing has completed.";s:11:"description";s:143:"This function is called any time a new item is created in the store.
It is called immediately after the store newItem processing has completed.";s:14:"return_summary";s:8:"Nothing.";}s:35:"dojo.data.api.Notification.onDelete";a:7:{s:9:"prototype";s:26:"dojo.data.api.Notification";s:4:"type";s:8:"Function";s:10:"parameters";a:1:{s:11:"deletedItem";a:2:{s:4:"type";s:4:"item";s:7:"summary";s:17:"The item deleted.";}}s:6:"source";s:76:"		throw new Error('Unimplemented API: dojo.data.api.Notification.onDelete');";s:7:"summary";s:145:"This function is called any time an item is deleted from the store.
It is called immediately after the store deleteItem processing has completed.";s:11:"description";s:145:"This function is called any time an item is deleted from the store.
It is called immediately after the store deleteItem processing has completed.";s:14:"return_summary";s:8:"Nothing.";}s:13:"dojo.data.api";a:2:{s:4:"type";s:6:"Object";s:7:"summary";s:0:"";}s:9:"dojo.data";a:2:{s:4:"type";s:6:"Object";s:7:"summary";s:0:"";}s:4:"dojo";a:2:{s:4:"type";s:6:"Object";s:7:"summary";s:0:"";}}