Design PrinciplesThe Application Programmer's Interface for all readers has been designed with the following principles:
Network - Given the widespread use of networks in corporate environments, the API is based on TCP/IP networking, the underlying protocol of the Internet and many private networks. A variety of network services provide remote clients access to the functionality of the reader. Flexibility - Conventional embedded systems usually have hard coded command protocols, which means the application writer is limited to the flexibility that the system designer put in. In the Magellan reader system, the programmer uses a scripting language to control the reader. The power of this language allows programmers to implement functionality on the reader that the reader designers had not considered. Intelligent - Readers can be programmed with scripts to automatically respond to tags in the way most appropriate to the end user application. This way, the performance of the system is not limited by communications overhead to the user's system. Portability - All interaction with a reader is based on plain text. This avoids platform and operating system dependencies such as byte ordering, byte padding and locale. This is common for many network based servers, such as Web and e-mail. Consistency - An application written for one reader should work with all readers. A given operation has the same name in all readers. Differences in reader hardware are accommodated as transparently as possible.
Communicating With A Reader
|
Related items
|