<br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Using jingle for file transfer makes sense from a provider<br>perspective, regarding relay cost and speed. But for clients, I feel
<br>that we are reinventing the wheel (TCP in this case, and it's a big<br>wheel), and that we are trying to solve a problem that does not need<br>solving right now.</blockquote><div><br>Providers will be very reluctant to provide relay without any bandwidth caps. Because of this, the transfer approach turns into a user problem: users want the fastest transfer, which they will have with a direct, non-relayed stream. Solutions that optimize for direct streams will provide the best user experience. In this regard Jingle is a good choice because of the high percentage of direct, non-relayed connections (92% of the time).