[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #28942 [Circumvention/Snowflake]: Evaluate pion WebRTC
#28942: Evaluate pion WebRTC
-------------------------------------+-------------------------------
Reporter: backkem | Owner: cohosh
Type: enhancement | Status: accepted
Priority: Medium | Milestone:
Component: Circumvention/Snowflake | Version:
Severity: Normal | Resolution:
Keywords: ex-sponsor-19 | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor: Sponsor28-can
-------------------------------------+-------------------------------
Comment (by backkem):
I wanted to quickly reiterate that this is one of the reasons for
existence of our (Pion WebRTC) detach API. It provides you with an
io.ReadWriter. With this pattern the upper layer protocol (your protocol)
can supply the buffer for reading/writing. This means, since you likely
know what the appropriate buffer size is for your use-case, you can
allocate it accordingly. There is actually a [https://github.com/w3c
/webrtc-pc/issues/1732 long running issue] to expose this in the WebRTC
API. More modern web APIs are modeled in a similar way, E.g.:
[https://wicg.github.io/web-transport/#incoming-stream* incoming-stream] &
[https://wicg.github.io/web-transport/#outgoing-stream* outgoing-stream].
To ensure compatibility with other WebRTC implementations it is of-course
still recommended to respect the buffer-size limits mentioned in Lennart's
blog post.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28942#comment:32>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs