Skip to content

Conversation

kylecarbs
Copy link
Contributor

The maximum was hardcoded at 4MB. This allows it to
be configurable for larger payloads. An option is
exposed in dprcmanager.Options.

@kylecarbs
Copy link
Contributor Author

Closes #29.

@zeebo
Copy link
Collaborator

zeebo commented Apr 24, 2022

Unfortunately, changing NewReader to take a new parameter is an API breaking change. Instead, can we add a new NewReaderOptions function that takes a ReaderOptions struct type and change NewReader to call that?

@kylecarbs
Copy link
Contributor Author

Yup! I had that initially but wanted to stay consistent with NewWriter. I shall update!

The maximum was hardcoded at 4MB. This allows it to
be configurable for larger payloads. An option is
exposed in `dprcmanager.Options`.
@kylecarbs kylecarbs force-pushed the main branch 2 times, most recently from 550b607 to d6d4c88 Compare April 24, 2022 20:20
@kylecarbs
Copy link
Contributor Author

@zeebo it's been updated!

@egonelbre egonelbre merged commit 56b3e4e into storj:main Apr 25, 2022
kylecarbs added a commit to kylecarbs/drpc that referenced this pull request Jun 21, 2022
* drpcwire: expose buffer size on Reader (storj#30)

The maximum was hardcoded at 4MB. This allows it to
be configurable for larger payloads. An option is
exposed in `dprcmanager.Options`.

* regen docs

Change-Id: I04ac7c0c5bea05a95ee38cd0584ca624ce60f077

* Don't reuse buffer after Write()

Signed-off-by: Spike Curtis <[email protected]>

Co-authored-by: Kyle Carberry <[email protected]>
Co-authored-by: Jeff Wendling <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants