You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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 argumentchunk_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)
The text was updated successfully, but these errors were encountered: