Justin, Thanks for your reply. I implemented it this way (and it works):
1. I register the FLVReader to a FLVKeyFrameAnalyzer class as soon a request for a file (the keyframe data) comes in. 2. The first connection that requests the particular file is the 'owner' of the keyframe-reading process 3. As soon as the first process is done, it notifies the FLVKeyFrameAnalyzer class its completion, which in its turn notifies all interrupted FLVReaders through a callback method that is it done. This callbackmethod also provides the direct data (copied) to the interrupted listeners At last, the analyzer management class destroys al references to the fist connection and the listener and everyone is happy. The only 'problem' I am still having is that the listening (interrupted) connections go into wait state until they have keyFramMetaData, set through the callback method. I think this is not particularly fancy, so there is room for improvement by checking if the connection requesting the file is still active. Will do that later. I am fine for now. /Rob _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
