Use the Jetstream REST API to queue commands for your offline devices. When devices are online, commands are not queued; they are executed immediately. The Jetstream REST API may also be used to configure your application. Use GetEvents to begin receiving Jetstream events from deployed devices.
Jetstream devices usually communicate in near realtime utilizing websocket technology. When the devices are actively communicating, they are said to be "online". When there are communication outages, the devices are said to be "offline". When devices are offline, any commands issued to the devices are queued for delivery when the device re-establishes communications. Similarly, any events the device publishes are held until the device comes online again.
For developers just getting started, we recommend going through the Jetstream Developers Guide and logging in to the Admin Console to add a device and simulate events. When you are ready to develop, use the Jetstream tools and open source projects to aid you in your journey.
Jetstream lets you execute commands for your RFID devices. Devices can be placed on any internet based network; therefore, Jetstream will handle all the complexity of coordinating the delivery, execution and returning the results of your command request. When your devices have are online with Jetstream the commands are executed immediately. If your device if offline the commands are queued until the device establishes the conneciton.To Execute a Command
CommandId is the unique identifier to correlate the command request with the resulting CommandCompletionEvent
At any time you may reconfigure your Jetstream application to add or remove devices, get your current application configuration, determine what types of devices are available to add or keep your devices configured to meet a policy.To Configure Your Application
Jetstream automatically publishes device and system events to your application.To Receive an Event
Jetstream supports multiple RFID device types and abstracts the type of device from your application. Therefore you can configure, command and receive events from any device using the same code. Device metadata is managed through DeviceDefintion which allows devices to define the commands and config values it supports in Jetstream. Device types that support more than just the standard commands can define their own commands using the DeviceSpecificCommand. Finally devices that require custom event data can publish their event data with the standard events using the DeviceExtension elements found in the standard event schemas.