-
Notifications
You must be signed in to change notification settings - Fork 418
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
Async streaming #86
Comments
You don't have other choice but implement outbound queue. Inbound queue is implemented already |
Yes I saw it, and started to add a outbound. But the Stream constructor and some other stuff made me a bit unsure if two queues would be the best option rather than a shared with a tag indicating if the message will be sent out, or is incomming. But thanks for feedback, I'll look on the two queue way 👍 |
Inbound and outbound queues are independent. |
Aha ok, I will probably need to rewrite/copy/write-a-similar SendPacket as well? More like the ConcatenatePackets, because of the senario where buffer size > max_package_size ? |
No. You don't need to concatenate packets. |
Ok, so more or less it's just about pushing queued packets into SendPacket, and it will take care of it? |
You should read how TCP protocol works, then it will be clear what ti do |
Will do, and try to solve this issue :) |
Issues moved to https://track.privacysolutions.no |
I'm looking at the streaming now. Would it be best with two queues? One for receive and one for sending? or maybe merge them, with a tag in the packet struct with to be sent "in" or "out"?
The text was updated successfully, but these errors were encountered: