Real time fetch and show #956

New Issue

GiteaMirror · 2025-11-02T03:43:13-06:00

GiteaMirror commented

2025-11-02 03:43:13 -06:00

Originally created by @mmarif4u on GitHub (Aug 10, 2017).

Currently i guess there is no ajax technology used for fetch and show things specifically in issues comment system and notifications which can reduce the load of refresh and will be more real time instead. Means, that i no need to refresh to know that some one commented on the issue or i have notifications for action.

There could be other areas which also can have this feature for usability and better productivity.

Any thoughts?

Originally created by @mmarif4u on GitHub (Aug 10, 2017). Currently i guess there is no ajax technology used for fetch and show things specifically in issues comment system and notifications which can reduce the load of refresh and will be more real time instead. Means, that i no need to refresh to know that some one commented on the issue or i have notifications for action. There could be other areas which also can have this feature for usability and better productivity. Any thoughts?

GiteaMirror added the topic/ui issue/confirmed type/enhancement labels 2025-11-02 03:43:13 -06:00

GiteaMirror commented

2025-11-02 03:43:14 -06:00

@sapk commented on GitHub (Aug 10, 2017):

Some of the pages use Vue to display dynamic content. The improvement of api and the related documentation is the first step and we are going in that direction but we try to keep in mind that some folk disable JS and gitea should still be usable in those cases.

@sapk commented on GitHub (Aug 10, 2017): Some of the pages use Vue to display dynamic content. The improvement of api and the related documentation is the first step and we are going in that direction but we try to keep in mind that some folk disable JS and gitea should still be usable in those cases.

GiteaMirror commented

2025-11-02 03:43:14 -06:00

@lafriks commented on GitHub (Aug 10, 2017):

I think it should be done using websockets just like github is doing it with notification and link "Refresh"

@lafriks commented on GitHub (Aug 10, 2017): I think it should be done using websockets just like github is doing it with notification and link "Refresh"

GiteaMirror commented

2025-11-02 03:43:14 -06:00

@mmarif4u commented on GitHub (Aug 20, 2017):

Websockets would be great for two way communication for stuffs like updating the notification counter/badge, pulling the latest comments etc.

@mmarif4u commented on GitHub (Aug 20, 2017): Websockets would be great for two way communication for stuffs like updating the notification counter/badge, pulling the latest comments etc.

GiteaMirror commented

2025-11-02 03:43:14 -06:00

@bkcsoft commented on GitHub (Aug 24, 2017):

Anyone here tried having 10000 websockets open to the same server? :trollface:

EDIT: My point being, use long-polling with ETAGs instead... it's usually much faster

@bkcsoft commented on GitHub (Aug 24, 2017): Anyone here tried having 10000 websockets open to the same server? :trollface: EDIT: My point being, use long-polling with ETAGs instead... it's usually much faster

GiteaMirror commented

2025-11-02 03:43:15 -06:00

@andrew-boyarshin commented on GitHub (Nov 11, 2017):

@bkcsoft I love using this golang websocket library. It's super fast, has zero-copy upgrade and was designed specifically to handle heavy loads.

@andrew-boyarshin commented on GitHub (Nov 11, 2017): @bkcsoft I love using [this](https://github.com/gobwas/ws) golang websocket library. It's super fast, has zero-copy upgrade and was designed specifically to handle heavy loads.

GiteaMirror commented

2025-11-02 03:43:15 -06:00

@stale[bot] commented on GitHub (Feb 11, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 11, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror referenced this issue

2025-11-02 11:52:06 -06:00

[PR #956] [MERGED] Refactor notificationsForUser since xorm In support slice of customer… #15677

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#956