You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create the base class to be used by both the kiosk and gate/reader device simulators as well as the base event message (which includes: device type (string), device id (string), message type (string), and timestamp (timestamp)).
Recommended implementation will be a C#/.Net Core UWP application. Will evaluate other options based on team skill sets.
Common Device Properties include: device type (string), device id (string), station/location (string), metadata version (string), state (enabled/disabled/failed)
Devices will be run on developer workstations at first, but may be deployed to Azure VMs for continual testing (time allowing). May consider containerization depending on team skill sets. Device simulator will have a "common" foundation class and the two specific devices will inherit from that one.
All operations in the simulated device will write out to a local file. These log files can optionally contain periodic rotation and file curling (removing older files) if time allows).
The base device will include a single "send message" function that will be used to send any messages.
The text was updated successfully, but these errors were encountered:
Intent is that simulated devices would first be tested using the local developer workstations. As the project continues, simulated devices may run in Azure VMs or if time allows, as containerized Windows applications running in Azure Function instances.
Create the base class to be used by both the kiosk and gate/reader device simulators as well as the base event message (which includes: device type (string), device id (string), message type (string), and timestamp (timestamp)).
Recommended implementation will be a C#/.Net Core UWP application. Will evaluate other options based on team skill sets.
Common Device Properties include: device type (string), device id (string), station/location (string), metadata version (string), state (enabled/disabled/failed)
Devices will be run on developer workstations at first, but may be deployed to Azure VMs for continual testing (time allowing). May consider containerization depending on team skill sets. Device simulator will have a "common" foundation class and the two specific devices will inherit from that one.
All operations in the simulated device will write out to a local file. These log files can optionally contain periodic rotation and file curling (removing older files) if time allows).
The base device will include a single "send message" function that will be used to send any messages.
The text was updated successfully, but these errors were encountered: