-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Participant check-in by receptionist should trigger web service call #25
Labels
Comments
gregorwolf
added a commit
that referenced
this issue
Oct 3, 2016
gregorwolf
added a commit
that referenced
this issue
Oct 4, 2016
gregorwolf
added a commit
that referenced
this issue
Oct 4, 2016
gregorwolf
added a commit
that referenced
this issue
Oct 5, 2016
gregorwolf
added a commit
that referenced
this issue
Oct 5, 2016
gregorwolf
added a commit
that referenced
this issue
Oct 5, 2016
gregorwolf
added a commit
that referenced
this issue
Oct 6, 2016
gregorwolf
added a commit
that referenced
this issue
Oct 6, 2016
gregorwolf
added a commit
that referenced
this issue
Oct 7, 2016
gregorwolf
added a commit
that referenced
this issue
Oct 7, 2016
gregorwolf
added a commit
that referenced
this issue
Oct 7, 2016
open-ui5
pushed a commit
to open-ui5/SITreg
that referenced
this issue
Oct 14, 2016
open-ui5
pushed a commit
to open-ui5/SITreg
that referenced
this issue
Oct 14, 2016
open-ui5
pushed a commit
to open-ui5/SITreg
that referenced
this issue
Oct 14, 2016
open-ui5
pushed a commit
to open-ui5/SITreg
that referenced
this issue
Oct 14, 2016
open-ui5
pushed a commit
to open-ui5/SITreg
that referenced
this issue
Oct 14, 2016
open-ui5
pushed a commit
to open-ui5/SITreg
that referenced
this issue
Oct 14, 2016
open-ui5
pushed a commit
to open-ui5/SITreg
that referenced
this issue
Oct 14, 2016
open-ui5
pushed a commit
to open-ui5/SITreg
that referenced
this issue
Oct 14, 2016
open-ui5
pushed a commit
to open-ui5/SITreg
that referenced
this issue
Oct 14, 2016
open-ui5
pushed a commit
to open-ui5/SITreg
that referenced
this issue
Oct 14, 2016
open-ui5
pushed a commit
to open-ui5/SITreg
that referenced
this issue
Oct 14, 2016
open-ui5
pushed a commit
to open-ui5/SITreg
that referenced
this issue
Oct 14, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To print i.e. badges for the visitors it should be possible to call a web service. To allow devices to be connected via push rather than pull I will use the HCP IoT Services. It allows devices to establish a web socket connection.
To allow different devices (also multiple devices) for the same event a Device entity with the fields EventID, History, Active, DeviceID (Char Lengh 36 according to the HCP IoT Documentation for Device) needs to be created. This table is exposed in the OData service for the organizer. It can be maintained like the co-organizer table.
As the devices might not be able to send a confirmation back that i.e. the badge was printed also a table that queues the messages. This table should have the Columns ParticipantID, EventID, FirstName, LastName, Twitter, SendStatus, History. This table is exposed in the receptionist OData service. So the receptionist can confirm when the output is finished. Then the next in the queue can be sent.
The text was updated successfully, but these errors were encountered: