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

Expose message fragmentation #1638

Open
skreborn opened this issue Dec 8, 2024 · 0 comments
Open

Expose message fragmentation #1638

skreborn opened this issue Dec 8, 2024 · 0 comments
Labels
new feature Something new is needed

Comments

@skreborn
Copy link

skreborn commented Dec 8, 2024

Currently, Zenoh performs internal fragmentation for large messages. While this allows it to transfer the message reliably, it provides no way for the developer to access the progress of this process.

To circumvent this, one has to manually fragment messages, which introduces complexity as well as duplication of work and reduction of performance.

This would be most beneficial when transferring large binary blobs, like files, to keep track of the transfer process and provide accurate predictions about their expected delivery time.

One possibility would be to provide an interface that streams fragments in and out of publishers and subscribers respectively, which would have the added benefit of not necessarily having to store the entire blob in memory on either side of the transfer.

@skreborn skreborn added the new feature Something new is needed label Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new feature Something new is needed
Projects
None yet
Development

No branches or pull requests

1 participant