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

Allow modifying the socket chunk-size #46

Closed
exhuma opened this issue Jun 14, 2018 · 1 comment
Closed

Allow modifying the socket chunk-size #46

exhuma opened this issue Jun 14, 2018 · 1 comment

Comments

@exhuma
Copy link
Owner

exhuma commented Jun 14, 2018

Currently the chunk-size for socket reading is hardcoded to 4096 bytes. This value could be made configurable for the end-user. This is kind of related to #45 as it may reduce the chance of running into #45. However, fixing #45 has priority!

This is also related to #1 as it is another configuration value for the network behaviour.

Currently the timeout value is exposed by most top-level functions. To guarantee backwards-compatibility a new argument chunk_size should be introduced.

For the next major release, this would make more sense in the creation of an SNMP-Client instance (see also #3)

@exhuma
Copy link
Owner Author

exhuma commented Jan 11, 2019

The value is currently accessible via the global module-level variable puresnmp.transport.BUFFER_SIZE.

It can be modified by setting the value before making a call to an SNMP function.

@exhuma exhuma closed this as completed Jan 11, 2019
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