Confirm
368
edits
Changes
→More information: add explanation about activity names
== More information ==
Some various explanation regarding part of this API that are not self-explanatory.
=== Activity names ===
Basic activities will have simple names like ''edit'', ''view'', ''pick'' or ''share'' (this is non-exhaustive). A set of basic activities should be define in the initial specification. Defininig will imply specifying how ''data'' should be structured to be considered valid and how the return value (if any) should be structured too.
Any other specification will be able to create new activities. For example, a Messaging specification might add 'send-sms'.
Any application will be able to create new activities. Any application is able to register itself as handling the activity ''foobar'' and any application is able to start the activity ''foobar''.<br>
However, to prevent naming collision, we recommend such proprietary naming to be prefixed with an URL. For example: ''example.org/foobar'' or ''org.example.foobar'' (doesn't matter that much).
=== Handling an activiy ===
Handling activities will be done trough [https://groups.google.com/group/mozilla.dev.webapi/browse_thread/thread/a3c6e4c31d04b663/ System Message Handler]. An ''ActivityHandlerRequest'' will be passed in the Message.
