RIPT trives to get rid of ICE and use HTTP/3 with existing backends. It does not support peer to peer.
Den 6. april 2020 23:28:08 CEST, skrev Christer Holmberg <christer.holmberg=40ericsson.com@xxxxxxxxxxxxxx>:
Hi,
>>> There should be no benefit to native app except for vendor lock-in.
>>
>> Well, don't discount vendor lock-in. But of course if the app can
>> communicate directly between peers, whereas the browser cannot, that
>> consumes fewer resources than routing the traffic through the vendor's
>> servers, and likely provides better service to users also. An app is
>> also better positioned to act as spyware.
>
> WebRTC was designed to allow communication directly between peers.
> Much of the complexity in the stack (which RIPT is trying to get rid of)
> comes precisely from the decision to make it peer to peer.
As far a peer to peer communication is concerned, what complexity does RIPT get rid of?
Regards,
Christer
--
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
