Added requestStreamOption to endpointProvider, updated interopBroker …

…and added notification examples (#725)



Updated existing modules and template

* Introducing stream support to endpoints an example of being able to request notifications

We include examples of notifications being triggered via the platform using the channel api or intents.

* Additional scenarios covered.

- Updated WPS Interop Broker implementation so that it includes fdc3 app instances if they exist in the array of apps returned when findIntent is called as recommended by the FDC3 documentation.
- Extended endpoint so that we now have a requestStream option for those implementing endpoints that want to return a stream of data instead of a simply requestResponse.
- Included an example of the the requestStream endpoint by implementing an example source of notification data in the modules/endpoint/example-notification-source
- Added an example of a lifecycle module that handles notifications coming from the notification source as well as notifications that have been sent to it. This shows how you can standardize some types of notification actions: raise-intent, launch-app, broadcast (option to broadcast on an app channel or user channel). This is just an example showing how you could expose an API to your content using an SDK approach using the Channel API or intents. This is a basic example and there are many more things to consider but it is intended as an example for a discussion around options.

how-to/workspace-platform-starter-basic/public/apps.json

@@ -38,9 +38,7 @@
 		"supportEmail": "[email protected]",
 		"publisher": "OpenFin",
 		"intents": [],
-		"images": [
-
-		],
+		"images": [],
 		"tags": ["page", "openfin", "client", "interop", "fdc3", "contact"]
 	},
 	{
@@ -59,9 +57,7 @@
 		"supportEmail": "[email protected]",
 		"publisher": "OpenFin",
 		"intents": [],
-		"images": [
-
-		],
+		"images": [],
 		"tags": ["page", "openfin", "client", "interop", "fdc3", "contact"]
 	}
 ]