Currently two configuration lines are necessary to initiate ICEpush as a service

<script type="text/javascript" src="http://labs.icesoft.com/push/code.icepush"></script>

<script type="text/javascript">
ice.push.configuration.contextPath = "http://labs.icesoft.com/push/";
</script>

This can be reduced to a single bridgeit configuration of "http://labs.icesoft.com/push/".

bridgeit.usePushService("http://labs.icesoft.com/push/", apiKey)

The essential features from ICEpush are covered by: createPushId, addGroupMember, register, resumeConnection*, pauseConnection*. not called by application, will be integrated with bridgeit.js or code.icepush.

To be added to bridgeit.js in http://server.ice:8888/svn/ossrepo/icemobile/branches/icemobile-bridgeit-transition/icemobile/bridgeit/src/main/javascript/bridgeit.js

bridgeit.usePushService(serviceURL, apiKey)

bridgeit.addPushListener(groupName, callback)

bridgeit.push(groupName, options)

Implementation must have a friendly warning in the console if invoked without ICEpush being loaded via usePushService():

"BridgeIt push cannot be used without a push service. Please set one up with bridgeit.usePushService(serviceURL, apiKey)"

Typical application use will be:

Perhaps in the head, but potentially elsewhere on the page:

<script>
bridgeit.usePushService("http://labs.icesoft.com/push/", "deadbeef")
</script>

In the output portion of the application:
<script>
bridgeit.addPushListener("chat", handleChat);
</script>

On an input control

<button onclick='bridgeit.push("chat");'>Send Chat</button>

Modified ICEpush to publish startConnection method so that dynamic setups can start the blocking connection without relying on document load. The method can be accessed at ice.push.connection.startConnection.

Implemented usePushService, addPushListener and push functions. Also tested their functionality successfully.

usePushService() might be called multiple times. Would this have any side effects? (From the code it looks like the eval could run multiple times, so this should likely be guarded against.)

Reopening to address potential issues from redundant initialization.

Implemented detection and blocking of redundant initialisation.

The following strange code was added to bridgeit.push:

         if (ice && ice.push && ice.push.configuration.contextPath) {
-            ice.push.notify(groupName, options);
+            if (options && options.delay)  {
+                ice.push.notify(groupName, options, options);
+            } else {
+                ice.push.notify(groupName, options);
+            }
         } else {

We likely do not need separate options objects in the notify call.

Reopened to consider merged options parameter.

Comment from Deryk: If BridgeIt provides a general services platform, all services should be accessible in a uniform way. For instance, a single API key should be provided only once for both the push service, location service, and echo service.

Instead of usePushService(), an extension would be useService("http://bridgeit.mobi","push","echo") which would dynamically download the required APIs and inject them under the bridgeit.* namespace using the first argument as the base service URL. The API key could be set in a separate call bridgeit.authorize(apikey).
Note that this requires the dependent services to be BridgeIt-aware to add their APIs under bridgeit. (icepush.js could detect window.bridgeit and add the required functions.)

Created issue PUSH-285 to define the merging of the 'options' parameter task.

There are two forms of the API to load services:

bridgeit.useService("http://api.bridgeit.mobi/","push","echo")

Services at different base URLs can be specified with multiple invocations of useService().

If the version of the service needs to be specified, the service can be registered in detail:

bridgeit.useService("http://api.bridgeit.mobi/","push",

)

Each service must have a script file stored at a well-known location, for instance:

http://api.bridgeit.mobi/echo/echo.js

The script echo.js will then add its API to the bridgeit object.

Initial integration is implemented.