jimfcarroll/xbmc — comment on commit fa29541976001a729f84b4713b34b14e36295582
File:  line 0
By FernetMenta:

`Do you gain an advantage in locking the DisplaySection separately from the DecoderSection?`
Yes, that's the work around. DecoderSection is locked in read mode for a relatively long time. In case on an error the variable protected by DisplaySection has to be written to.

Thanks for taking the time discussing this with me. At least I have doubts now if it's a good idea having reentrant read/write locks. The current design of vdpau is quite simple but I have a version where the object is accessed by four different threads and I was thinking about a better design.

`Or we could just move the entire codebase to an Actors model ;-)`
Yeah! Indeed a good idea. I am experimenting with this and have implemented a class following this approach. If you are bored you can take a look and tell me what you think. The interesting part is StateMachine()
https://github.com/FernetMenta/xbmc/blob/merge/xbmc/cores/dvdplayer/DVDPlayerVideoOutput.cpp

Thanks again. I think for now we don't need to change anything.