Allow configuration of a data size before a flush occurs #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the client gets flushed every command (which is every pixel) this is inefficient since every tcp package can hold multiple pixel (the exact number depends on the network and mtu).
This patch gives 3 options for setting a FlushMode:
- Manual > Never flush
- Commands > Flush after a number of commands (like Pixels)
- Bytes > Flush when a package size is reached.