WebSocket integration 2.0 #260

New Issue

Closed

opened 2023-05-09 00:00:15 +02:00 by blacklight · 0 comments

blacklight commented

2023-05-09 00:00:15 +02:00

Owner

The websocket service should be managed by the HTTP server's webapp itself - we shouldn't use a separate service listening on a different port
The service should have at least two distinct endpoints:
- /ws/events to submit/listen for events
- /ws/requests to submit requests and listen for responses
The service should implement strong authentication using the same logic used for the Flask routes
Remove the legacy backend.websocket

- [x] The websocket service should be managed by the HTTP server's webapp itself - we shouldn't use a separate service listening on a different port - [x] The service should have at least two distinct endpoints: - [x] `/ws/events` to submit/listen for events - [x] `/ws/requests` to submit requests and listen for responses - [x] The service should implement strong authentication using the same logic used for the Flask routes - [x] Remove the legacy `backend.websocket`

blacklight added the

label 2023-05-09 00:00:15 +02:00

blacklight self-assigned this 2023-05-09 00:00:15 +02:00

blacklight added this to the core project 2023-05-09 00:00:15 +02:00

blacklight referenced this issue from a commit

2023-05-09 00:04:15 +02:00

[#260] Implemented authentication for websocket routes.

blacklight added the

label 2023-05-09 00:07:32 +02:00

blacklight referenced this issue from a commit

2023-05-09 02:19:39 +02:00

[#260] Support for sending events via websocket over `/ws/events`.

blacklight referenced this issue from a commit

2023-05-09 02:47:27 +02:00

[#260] Added ``/ws/requests`` websocket route.

blacklight referenced this issue from a commit

2023-05-09 02:47:27 +02:00

[#260] Removed legacy `backend.websocket`.

blacklight closed this issue

2023-05-09 02:47:49 +02:00

blacklight referenced this issue from a commit

2023-05-11 00:44:24 +02:00

[#260] A simple entities caching mechanism using the browser storage.

Sign in to join this conversation.

No Label

good first issue

waiting user input

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

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

No due date set.

Dependencies

No dependencies set.

Reference: platypush/platypush#260

No description provided.