Joachim, Sorry for my lack of understanding.
According to APPSERVER-177 this issue was resolved. So why do we have this disclaimer about use at your own risk statement regarding trunk update 2231? What am I missing here? So this is mainly related to Shared Objects? Is this issue related to SN-1 reported by Victor? I just want to make sure I don't stumble into an area that I cannot resolved anything. Regards, Lenny On 8/22/07, Joachim Bauch <[EMAIL PROTECTED]> wrote: > > Hi Lenny, > > Lenny Sorey schrieb: > > Since the following statement is still in the description for this > > update, exactly what are we risking > > and what do we do if we have problems with this trunk update? > > > > Use at your own risk since packets may get "messed up". > > > > What is the remedy for this? How do we know if the Packets are " Messed > > Up" : ) > > messed up packets = FP might crash with an AV > > That can happen if lots of packets are sent by the server, triggered from > different sources (aka threads), like multiple clients updating a SO > _very_ fast. > > Check out APPSERVER-177 for details. > > Joachim > > > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org > > >
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
