beautypg.com

Destroy, Uri syntax, Destroy 22 uri syntax 22 – ThingMagic Mercury API v1.23.0 User Manual

Page 22

background image

Connecting to Readers

22

Level 1 API

Destroy

When the user is done with the Reader,

Reader.destroy() should be called to

release resources that the API has acquired, particularly the serial device or network
connection:

void destroy()

In languages that support finalization, this routine should be called automatically;
however, since languages that support finalization do not generally guarantee when or
whether they will be invoked, explicitly calling the

destroy() method to guarantee

release is highly recommended.

Multiple

Reader objects may be obtained for different readers. The behavior of

create() called repeatedly with the same URI without an intervening destroy() is not
defined.

URI Syntax

The URI argument follows a subset of the standard RFC 3986 syntax:

scheme://authority/path

The

scheme defines the protocol that will be used to communicate with the reader. the

supported “schemes” for ThingMagic devices are:



tmr - (ThingMagic Reader) indicates the API should attempt to detemine the protocol

and connect accordingly. The API will select among eapi, rql, and llrp, but any
custom serial protocols, such as tcp will have to be explicitly specified.



eapi - indicates a connection to a

SerialReader

type device via a COM port (or a USB

interface acting as a virtual COM port).



rql - indicates a connection to an

RqlReader

type device.



llrp - indicates a connection to an

LLRPReader

type device.

The

authority specifies an Internet address and optional port number for protocols

with network transport (currently only rql), or is left blank to specify the local system.

The

path is currently unused for rql and is used to specify the serial communications

device to which the reader is attached for eapi. The tmr scheme assumes that the
protocol is rql if there is a non-blank authority and a blank path, and the serial protocol if
the authority is blank and the path is non-blank. tmr is the preferred scheme.

The C#.NET API allows users to add custom transport interfaces for readers. The
samples include the URI “tcp”, which indicates a connection to an

SerialReader

type

device via a TCP bridge.