App to App communication using topics

Unfortunately, right now there is no additional documentation nor do I know of a sample. Which doesn't help much, I know.

What I do know is this:

* you must declare <topics> and add <topic publish="true"> for each topic that an App publishes. Typically, this would be like firing an event. You specify the payload as <property> elements inside <topic>. And <property> is allowed to be complex (recursive) to accommodate objects in the payload.

* Once you initialize an App that has a published topic, the App inherits the publish(object) method that you can use to publish messages for events in your App. The object must match your declared payload.

* you must declare <topics> (if not already) and add <topic subscribe="true"> to have an App subscribe to published messages. Generally, all you need is one subscription with a list of *all* properties for this App. This topic can then be used to receive published messages from any other App.

* in Apps that subscribe to topics, you must implement a receive(object) method to receive published messages.

* app-to-app communication is not *solely* programmatic/declarative. In other words, you cannot tightly wire Apps using the same topic names/payloads and then use the publish() and receive() methods. Apps *must* be wired in Mashboard for this to work. Wiring will handle the mapping between published/subscriber topic payloads and ensures that communication is handled appropriately at runtime.

* only Apps with <topic> in their spec are visible for wiring in Mashboard.

This may not be enough, but I hope it helps get you started. Samples and docs are in the works in this area.

 I found this example, it is "hello world" level but I think it might be helpful to get you started.

Israel @ JackBe