Skip to content
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

Open
dungwinux opened this issue Mar 29, 2019 · 6 comments
Open

HTTP Push for notification system ? #67

dungwinux opened this issue Mar 29, 2019 · 6 comments
Labels
enhancement New feature or request experimental Highly unstable, need further testing

Comments

@dungwinux
Copy link
Member

dungwinux commented Mar 29, 2019

  • As the title, let's implement socket.io Http push to send to front-end notifications, updates, ... (i.e submission's updates, new submissions, ...)
@dungwinux dungwinux added the enhancement New feature or request label May 29, 2019
@dungwinux dungwinux pinned this issue May 29, 2019
@dungwinux dungwinux unpinned this issue May 29, 2019
@minhducsun2002
Copy link
Contributor

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?

@minhducsun2002
Copy link
Contributor

Bump

@dungwinux dungwinux added the experimental Highly unstable, need further testing label Oct 10, 2019
@dungwinux dungwinux pinned this issue Oct 13, 2019
@dungwinux dungwinux changed the title WebSocket for notification system ? HTTP Push for notification system ? Mar 7, 2020
@minhducsun2002
Copy link
Contributor

Bump again. You can implement a WS server now to dispatch notifications.

@dungwinux
Copy link
Member Author

@minhducsun2002 See the title change ? HTTP Push is more preferable for sending notification

@minhducsun2002
Copy link
Contributor

minhducsun2002 commented Mar 26, 2020

We will need HTTPS. I mean, proper HTTPS, not self-signed certs.
Which seems to be impossible currently.

In detail, we will need a service worker on the client side. Which cannot be installed through HTTP.

@dungwinux
Copy link
Member Author

To implement WebSocket only for updating is overpowered.
Let's find some better alternatives.

@dungwinux dungwinux unpinned this issue Mar 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request experimental Highly unstable, need further testing
Projects
None yet
Development

No branches or pull requests

2 participants