How to make the connection reliable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



sorry, I am wrong, libnice just implement pseudo tcp as libjingle,  not rudp.

2010/11/25 Kabil Akp?nar <kabilakpinar at gmail.com>:
> 2010/11/25 bo shi <cnshibo at gmail.com>
>>
>> I only know libnice implement rudp in c, but based on glib.
>> udt maybe another selection, but the interface is not very fit for pjlib.
>
> Where exactly is rudp in libnice, can you point it?
>
>>
>> waiting good news from you.
>
> Once I am finished I will send you the integrated code also. So we can
> together evaluate the behaviour.
>>
>>
>>
>> 2010/11/25 Kabil Akp?nar <kabilakpinar at gmail.com>:
>> > in fact, I have already started porting enet with callbacks... I will
>> > let
>> > you know when I am finished, probably tomorrow, if everything goes well.
>> > And I will suggest you to port RUDP if you can, by the way, which rudp
>> > lib
>> > do you mean?
>> >
>> > 2010/11/24 bo shi <cnshibo at gmail.com>
>> >>
>> >> I am looking for such solution too.
>> >> I think we maybe need to port enet or other rudp libs.
>> >>
>> >> 2010/11/14 Kabil Akp?nar <kabilakpinar at gmail.com>:
>> >> > Hi All;
>> >> > I need some idea (although I have some) about making?the
>> >> > connection?reliable
>> >> > between peers. There are some open source libraries out there like
>> >> > enet
>> >> > rrunning on UDP. But the libraries in general, opens a server and
>> >> > client
>> >> > on
>> >> > UDP and sends the data reliably through the UDP channel. But ICE
>> >> > transport
>> >> > or STUN (which are very useful for traversing NATs) gives us a pair
>> >> > of
>> >> > callbacks as you know, not sockets.
>> >> > So what would your suggestion to integrate UDP based implementation
>> >> > to
>> >> > callback ones as it is in ICE, STUN or TURN.
>> >> > Thanks in advance.
>> >> >
>> >> > --
>> >> > Kabil Akp?nar
>> >> >
>> >> > _______________________________________________
>> >> > Visit our blog: http://blog.pjsip.org
>> >> >
>> >> > pjsip mailing list
>> >> > pjsip at lists.pjsip.org
>> >> > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>> >> >
>> >> >
>> >>
>> >> _______________________________________________
>> >> Visit our blog: http://blog.pjsip.org
>> >>
>> >> pjsip mailing list
>> >> pjsip at lists.pjsip.org
>> >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>> >
>> >
>> >
>> > --
>> > Kabil Akp?nar
>> >
>> > _______________________________________________
>> > Visit our blog: http://blog.pjsip.org
>> >
>> > pjsip mailing list
>> > pjsip at lists.pjsip.org
>> > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>> >
>> >
>>
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip at lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>
>
> --
> Kabil Akp?nar
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>



[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux