...

The PDS service provides 3 functions and responds to 5 events. The functions are as follows:

Functions

get_item

The get_item function takes two arguments. Both are required.

...

get_me

The get_me function takes one required argument.

...

get_all_me

The get_all_me function accepts no arguments. It returns all items from the entity's profile.

myProfile = pds:get_all_me();
 
returns at least ...
 
{
  "myProfileName" : "John Smith",
  "myProfilePhoto" : "data: image/png;base64, ...",
  "myProfileNotes" : "Nothing to see here, move along",
  "myProfileDescription" : "Be all you can bee"
}

Events

The PDS Service responds to 5 events. The events are as follows:

pds new_data_available

This event should be raised whenever you wish to add an item to the PDS. You should include three attributes to your event when raising it:

• namespace
  • A string containing the namespace to store the data
• keyvalue
  • A string containing the key to store the data under
• value
  • This attribute can be a string, number, boolean, hash, or array
  • This data gets stored in the PDS under the namespace and key

pds new_map_available

This event should be raised when you wish to update all items under a namespace. The items should be in a hash with the key being the value to update and the values being the values to be set as.

...

// These two new_data_available events are equivilent to the new_map_available event
raise pds event new_data_available
	with namespace = "test"
	and keyvalue = "foo"
	and value = "bar";
raise pds event new_data_available
	with namespace = "test"
	and keyvalue = "bar"
	and value = "cheese";
 
 
 
raise pds event new_map_available
	with namespace = "test"
	and mapvalues = {
		"foo" : "bar",
		"bar" : "cheese"
	};

web sessionReady

This event gets raised within the CloudOS when the user logs in. There are two things that happen when the session is ready:

...