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

sendBuffer should be accessible #750

Open
SwathingBlock opened this issue Aug 4, 2023 · 0 comments
Open

sendBuffer should be accessible #750

SwathingBlock opened this issue Aug 4, 2023 · 0 comments

Comments

@SwathingBlock
Copy link

The sendBuffer has a few issues.

  1. The buffer is essentially unlimited, so any message emited will ultimately be put on this buffer, meaning that it will potentially have a ridiculous amount of events. Ideally there should be a way to define a limit to this buffer with a FIFO policy.
  2. Buffer limit aside, there should be a way to clear this buffer, there are use cases where the user may need to implement his own queue because the queue on the Socket is too simple of an implementation, in which case the user may want to a short lived buffer by using the existing socket buffer but this queue may need to be cleared after a certain amount of time based on the user requirements.
@SwathingBlock SwathingBlock changed the title SendBuffered should be accessible sendBuffer should be accessible Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant