Browse Prior Art Database

A Better Method to Deliver a Sync API on Client Devices For Customers Disclosure Number: IPCOM000020057D
Original Publication Date: 2003-Oct-22
Included in the Prior Art Database: 2003-Oct-22
Document File: 1 page(s) / 5K

Publishing Venue



Cross Device API Solution to alleviate delivery and maintainenc of device specific programming libraries.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 91% of the total text.

Page 1 of 1

A Better Method to Deliver a Sync API on Client Devices For Customers

  The mobile device market is a heterogenious set of operating systems, native applications, and capabilities. Deliverying a consistent product on these differing devices is a difficult initiative. In addition, a full function product requires the delivery of an API library for component control. Providing an API library on many devices for component control of a delivered product is financially exhaustive and consistency is very difficult. The core idea of the solution is to remove the necessary development and version control and delivery of a native libary module for specific devices. The solution is for a client device API implementation as an HTTP GET command which alleviates the need of shipping and maintaining a library toolkit on different platforms. Each device can utilize the native programming language and execute a well formed HTTP request to the underlying service for the shipped product to provide component control. An example implementation is the Sync API that is used to sync components on a mobile device for the IBM Websphere Everyplace Access product[Request URI]

Where the request URI is defined as the following syntax

1. Run sync:


OR "/apisync?cmd=sync&sia=<commoncode>[&sia=<commoncode>]...."
2. Stop sync: "/apicync?cmd=stop"...