-
Notifications
You must be signed in to change notification settings - Fork 3
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
HTTP Push for notification system ? #67
Comments
Well, if there's any intention to create something like a messaging system for contestants to ask contest organizers for statement clarification, etc... Does it mean that an administrative front-end is required? |
Bump |
Bump again. You can implement a WS server now to dispatch notifications. |
@minhducsun2002 See the title change ? HTTP Push is more preferable for sending notification |
We will need HTTPS. I mean, proper HTTPS, not self-signed certs. In detail, we will need a service worker on the client side. Which cannot be installed through HTTP. |
To implement WebSocket only for updating is overpowered. |
socket.ioHttp push to send to front-end notifications, updates, ... (i.e submission's updates, new submissions, ...)The text was updated successfully, but these errors were encountered: