By Jason Brooks  |  Posted 2001-10-08 Print this article Print


In tests of Agentry, we could define sets of instructions that corresponded to the behaviors of an application. To create an application that logged products to be reviewed, for example, we created objects that related to a product, with fields for relevant information such as vendor name and ship date.

We could then link these objects to a back-end database using SQL statements and create screen sets that described what wed see on the target device.

Our test devices running the Agentry client would then receive the instruction sets and the back-end enterprise data during synchronization with the Agentry server over TCP/IP or over a serial link to an intervening desktop.

The resulting applications could run on Palm and Pocket PC devices alike, in each case taking on the look and feel of their host platforms, while carrying out the tasks wed set for them.

During subsequent synchronizations, the Agentry client would exchange data updates with the server and check for new or modified instruction sets. Agentry thereby offers developers the flexibility of WAP (Wireless Application Protocol), while shielding them from the network connectivity lapses that WAP is heir to.

As Editor in Chief of eWEEK Labs, Jason Brooks manages the Labs team and is responsible for eWEEK's print edition. Brooks joined eWEEK in 1999, and has covered wireless networking, office productivity suites, mobile devices, Windows, virtualization, and desktops and notebooks. JasonÔÇÖs coverage is currently focused on Linux and Unix operating systems, open-source software and licensing, cloud computing and Software as a Service. Follow Jason on Twitter at jasonbrooks, or reach him by email at

Submit a Comment

Loading Comments...
Manage your Newsletters: Login   Register My Newsletters

Rocket Fuel