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

Special case msg-rate == 0 to simply flush queues always? #454

Open
thommey opened this Issue Aug 29, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@thommey
Member

thommey commented Aug 29, 2017

Right now, msg-rate 0 doesn't circumvent the 1-second delay in the secondly() call to send a single message (or burst slightly). Maybe it would be good if that forced the burst, or even better, makes tputs() to the queue just immediately send it (or call the send-lines() function at least after queueing it).

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Sep 21, 2017

In most conversations I've been in, people assume [and hope] that msgrate == 0 means quick dequeuing / no queuing (analogous to using "putraw / putnow" usage). CAn this be made into the defaults (msgrate == 0 means no queueing)?

ghost commented Sep 21, 2017

In most conversations I've been in, people assume [and hope] that msgrate == 0 means quick dequeuing / no queuing (analogous to using "putraw / putnow" usage). CAn this be made into the defaults (msgrate == 0 means no queueing)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment