JSyncManager

From JSyncManagerWiki

Jump to: navigation, search

The jSyncManager

The jSyncManager is a pure Java API and application set for synchronizing PalmOS based devices with various types of computer systems.

The jSyncManager comprises the following components:

  • The jSyncManager API, an Object Oriented protocol stack set, with data accessor and conversion classes:
    • The jSyncManager Transports, used to abstract access to hardware and network layers (RS-232, USB, TCP/IP, etc.),
    • The jSyncManager Serial Protocol Stack, used to connect to handhelds across connections which don't provide their own framing and integretity checking,
    • The jSyncManager USB Protocol Stack, used to connect to handhelds across connections which do provide their own framing and integrity checking (USB, TCP/IP),
    • The jSyncManager Data Abstraction Classes, used to abstract PalmOS data types as standard Java classes and types,
    • The jSyncManager Data Conversion Classes, used to convert data to and from common data types (iCalendar, vCard, XML, CSV, etc.) to various PalmOS data formats,
    • The jConduit API, used to define and implement plug-ins to the jSyncManager Synchronization Engine to allow third parties to add their own synchronization logic for their own applications and databases,
    • The jSyncManager Synchronization Engine, used to manage a single instance of a complete jSyncManager protocol stack to provide high-level synchronization services.
  • The jSyncManager Core Application Set, which includes:
    • The jSyncManager Swing Client, a GUI-based application for synchronizing a handheld, providing logging facilities, jConduit Management, Transport selection, an Online Help Subsystem, and other options,
    • The jSyncManager Multiport Server, a server-style application which runs either from within a text console or as a daemon, providing simultaneous synchronization facilities for potentially hundreds of handhelds,
    • The Communications API Test Tool, for testing and detecting installation errors in the Java Communications API.

Additionally, the jSyncManager Project supports a number of separate, related sub-projects, including:

  • Error Transport, used to generate random errors within a serial transport instance in order to test data integrity routines (also useful for testing the maximum data damage the protocol stack can manage and still synchronize successfully),
  • OS/2 USB, a sub-project to implement a USB transport for IBM's OS/2 Operating System,
  • CDK-J Bridge, a special jConduit subsystem to permit conduits written to PalmSource's Conduit Developer Kit for Java (CDK-J) APIs on any platform,
  • The jSerial API, a specification and implementation for an RS-232 serial access library,
  • Plucker Support, a library to permit generating and working with [Plucker-based data in pure Java.



References:

Personal tools