Skip to content

Conversation

@dharjeezy
Copy link
Contributor

closes #352

…mi/buffer-size-webrtc-config

# Conflicts:
#	src/transport/webrtc/opening.rs
.parse()
.expect("valid multiaddress")],
datagram_buffer_size: 2048,
max_message_size: 512 * 1024,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where this constant is coming from? What is libp2p way of handling this?

What will happen in case of high throughput transfer — shouldn't we be able to parse the payload split over multiple max_message_size buffers?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should make this optional, not entirely sure if this interferes with @timwu20 upcoming work 🤔

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suggest hardcoding the constant from libp2p spec, as discussed in #352.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oki doki makes sense 🙏 Let's hardcode it instead

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.

webrtc: Optimize decoding with appropriate buffer size

3 participants