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

Remove fetch event #195

Closed
futurechimp opened this issue Apr 21, 2020 · 0 comments · Fixed by #208
Closed

Remove fetch event #195

futurechimp opened this issue Apr 21, 2020 · 0 comments · Fixed by #208
Assignees
Milestone

Comments

@futurechimp
Copy link
Contributor

We will deal with rate-limiting later, let's just get a simple and reliable system working first with websockets, and we can add (probably optional) rate-limiting later.

Practically speaking, any packet data that hits the gateway will either be

(a) sent down the websocket to a connected client (if one exists) or
(b) persisted to disk for later retrieval (if no there is no connected client)

In the (b) case, binary data will immediately be streamed down to the client when it connects, without any fetch message being necessary.

@futurechimp futurechimp added this to the 0.7.0 milestone Apr 21, 2020
@futurechimp futurechimp added this to Backlog in Core systems via automation Apr 21, 2020
@futurechimp futurechimp moved this from Backlog to In progress in Core systems Apr 21, 2020
@futurechimp futurechimp moved this from In progress to Backlog in Core systems Apr 21, 2020
@jstuczyn jstuczyn self-assigned this Apr 24, 2020
Core systems automation moved this from Backlog to Done Apr 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Core systems
  
Done
Development

Successfully merging a pull request may close this issue.

2 participants