[Live-devel] OutPacketBuffer::maxsize and multithreading

[PROMONET Michel]

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 ?

                Michel.


[@@THALES GROUP RESTRICTED@@]

De : live-devel-bounces at ns.live555.com [mailto:live-devel-bounces at 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 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 per-UsageEnvironment value instead of a global variable; this will overcome this problem.

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20120521/b453988f/attachment.html>