|
Hello,
Reading through your requirments, I would consider following:
Creating a PWA (with Angular or similar) which can be openend with an URL on the IPad. On first start the PWA creates a random token and stores it in the localstorage. Afterwards the IPad calls the Server over a websocket to register itself .
On the server there is an area for "incoming new devices" where the operator can accept the new device. The operator can send new tasks to the IPad over the Websocket. An optional extension would be to use Safari Push-Notifications to the WebApp even when it
is in the background.
I see no reason to use long-polling, because there are modern replacements of this concept. WebSockets (or native Push-Notifications) can be used to push tasks to the client.
Best Regards,
Wolfy
Von: WebObjects & WOnder Development im Auftrag von Markus Ruggiero (rucotec)
Gesendet: Sonntag, 10. April 2022 16:05
Bis: WebObjects & WOnder Development
Betreff: [WO-DEV] Need conceptual help
Dear WO-ers, I need your expertise.
I want to have a defined set of tablets (iPad) tied into my application. The tablets act as a satellite device in the context of a customer checking into a clinic. The person comes up to the registration desk and is checked in. The receptionist sees that there
is some registration data missing and hands the patient a tablet with the running application (or directs the customer to "use the green screen over there”). The receptionist should now be able to remotely open the registration screen on that green iPad, the
customer filling in the data and then pressing Save.
My train of thoughts goes like this:
As a one-time operation an admin opens the application from that green iPad, goes to a registration screen, and creates a “Satellite" entry in the database. This entry gets a UUID (or something similar) and that UUID should be put into the green iPads Web Storage.
This is a one-time registration of the device (actually the browser on that device, not the device itself).
When the workday starts the receptionist logs into the application on the green iPad and goes to a dedicated screen. This screen then polls every couple of seconds whether there is some task available on the server. There may be a number of different tasks
that the receptionist can create. The receptionist assigns such a task to the green iPad (or the red one or...) as an entry in the database and the polling iPad then displays the task screen. This kind of pushes a task to a browser. When the task is done the
iPad goes back to polling. The server also knows that the green iPad is busy or not.
I need to identify the polling iPad and I want to pre-register the iPad as a security measure.
How would you tackle such a requirement?
Thanks
---markus---
|