From: Stephens, A. <all...@wi...> - 2007-12-14 19:16:22
|
It would also help to know what version of TIPC Ming is using. The socket code has been improved in the TIPC 1.7 stream, which fixed a number of bugs. Regards, Al=20 > -----Original Message----- > From: tip...@li...=20 > [mailto:tip...@li...] On=20 > Behalf Of Randy MacLeod > Sent: Friday, December 14, 2007 12:28 AM > To: Ming Sun (xiansun) > Cc: tip...@li... > Subject: Re: [tipc-discussion] Multiple socket supported? >=20 > On Dec 13, 2007 9:25 PM, Ming Sun (xiansun) <xi...@ci...> wrote: > > > > I tried to create multiple RDM sockets and use different nameseq=20 > > addresses to receive message from different sources with select. > > But it is seems not reliable receive message from all=20 > sources once the=20 > > sender goes down and back up. >=20 > What exactly do you mean by "sender goes downa and back up"? > How do you know that messages appear to be dropped? >=20 > > Is multiple receiving socket in one thread supported? >=20 > Yes. >=20 > If you have a server which binds addresses A, B, C to three=20 > separate sockets then you will be able to call select() and=20 > receive messages. There is the usual limitation that if you=20 > are doing connectionless messaging, you have to do=20 > flow-control in your application code to avoid message drops=20 > if the server should fall too far behind. >=20 > If this doesn't help maybe you could post your test code. >=20 > -- > // Randy >=20 > -------------------------------------------------------------- > ----------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for just about=20 > anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.n > et/marketplace > _______________________________________________ > tipc-discussion mailing list > tip...@li... > https://lists.sourceforge.net/lists/listinfo/tipc-discussion >=20 |