Re: [Live-devel] OutPacketBuffer::maxsize and multithreading

2012-05-23 Thread Ross Finlayson
On May 21, 2012, at 8:00 PM, PROMONET Michel wrote: > We have make a try using thread local storage that is quite simple. > Adding "__thread" before OutPacketBuffer::maxSize declaration and definition > give a different variable for each threads. > > Do you think this fix is acceptable ? No,

Re: [Live-devel] OutPacketBuffer::maxsize and multithreading

2012-05-21 Thread PROMONET Michel
De : live-devel-boun...@ns.live555.com [mailto:live-devel-boun...@ns.live555.com] De la part de Ross Finlayson Envoyé : vendredi 4 mai 2012 07:12 À : LIVE555 Streaming Media - development & use Objet : Re: [Live-devel] OutPacketBuffer::maxsize and multithreading (First, please do not post the

Re: [Live-devel] OutPacketBuffer::maxsize and multithreading

2012-05-09 Thread PROMONET Michel
eaming Media - development & use Objet : Re: [Live-devel] OutPacketBuffer::maxsize and multithreading (First, please do not post the same question to the list multiple times.) Yes, this is an issue, and is a good illustration why it's ill-advised to structure a LIVE555-based application u

Re: [Live-devel] OutPacketBuffer::maxsize and multithreading

2012-05-03 Thread Ross Finlayson
(First, please do not post the same question to the list multiple times.) Yes, this is an issue, and is a good illustration why it's ill-advised to structure a LIVE555-based application using multiple threads. However, in some future release, I'll make the "OutPacketBuffer::maxSize" variable a