Initial integration is implemented.

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.

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

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.)

Reopened to consider merged options parameter.