feat: SSE support for appropriate streamed GET endpoints #19

New Issue

sudharshan · 2019-08-26T13:44:50+08:00

sudharshan commented

2019-08-26 13:44:50 +08:00

Need proper SSE support for the endpoints like fetchContacts, fetchConversations etc.
Also we can remove the fetchConversation endpoint since all the conversations are streamed and cached anyway, the retrieval of a single conversation can be done as a filter in the front stream implementation.

Need proper SSE support for the endpoints like fetchContacts, fetchConversations etc. Also we can remove the fetchConversation endpoint since all the conversations are streamed and cached anyway, the retrieval of a single conversation can be done as a filter in the front stream implementation.

sudharshan added the

enhancement

help wanted

labels 2019-08-26 13:44:50 +08:00

daniel self-assigned this 2019-08-31 12:06:17 +08:00

ambrose closed this issue

2019-09-24 18:47:30 +08:00

ambrose reopened this issue

2019-09-24 18:47:39 +08:00

ambrose commented

2019-09-24 18:48:18 +08:00

GET /user/contact
GET /user/conversation
Get /user
GET /user/conversation/:conversation/member

``` GET /user/contact GET /user/conversation Get /user GET /user/conversation/:conversation/member ```

❤️ 1

daniel commented

2019-09-28 21:23:05 +08:00

Include flag to turn NATs on and off.

sudharshan added the due date 2019-09-29

2019-09-28 21:24:17 +08:00

sudharshan modified the due date from 2019-09-29 to 2019-10-06

2019-09-28 21:24:36 +08:00

daniel referenced this issue from a commit

2019-10-06 23:22:14 +08:00

Resolves #19 added SSE subscribe streams

daniel closed this issue

2019-10-06 23:22:14 +08:00

Sign in to join this conversation.

No Label

No Milestone

No Assignees

3 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

2019-10-07

Dependencies

No dependencies set.

Reference: beep/backend-core#19