Yes, indeed ! However even thought that this is not officially supported the library works well using careful multi-threaded instance of the task scheduler object (see a post dated 2009-12-11). If you want each thread to have an independent NIC I'm afraid this could cause a potential issue because each thread might mess with those global variables.
Putting those variables in the socket object and adding a constructor to create the socket with a specific NIC would make the library much more thread safe. Thanks for the suggestion. GB >-----Original Message----- >From: live-devel-boun...@ns.live555.com [mailto:live-devel- >boun...@ns.live555.com] On Behalf Of Ross Finlayson >Sent: Wednesday, January 6, 2010 11:44 >To: LIVE555 Streaming Media - development & use >Subject: Re: [Live-devel] Multiple Network Adapter > >>If you have a system with multiple NIC interfaces is there a method or >>some standard way to tell the live555 library to which NIC (IP address) >>to bind the sockets created for the RTP streaming? Or I need to modify >>the code of the library to change the default behavior which seems to >be >>(in groupsockhelper.cpp): >> >>// By default, use INADDR_ANY for the sending and receiving interfaces: >>netAddressBits SendingInterfaceAddr = INADDR_ANY; >>netAddressBits ReceivingInterfaceAddr = INADDR_ANY; > >Those are global variables; not constants. So you don't need to >change the library code at all to change their values; just do so at >the start of your application - e.g. > ReceivingInterfaceAddre = our_inet_addr("10.0.1.2"); >-- > >Ross Finlayson >Live Networks, Inc. >http://www.live555.com/ >_______________________________________________ >live-devel mailing list >live-devel@lists.live555.com >http://lists.live555.com/mailman/listinfo/live-devel _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
