From: <bar...@t-...> - 2002-09-12 14:07:47
|
hallo michael, On 09/12, Michael Roitzsch wrote: > > > Sounds really good. Isn't xine_config_lookup_entry a candidate for > > > this? No we have an internal slot in the config structure, where > > > the entry from the lookup is copied to and then a pointer to this > > > slot is handed out. This can be problematic, when we have two calls > > > to > > > xine_config_lookup_entry from different threads, because one would > > > overwrite the config entry the other has requested. Allocating and > > > copying them on the caller's stack in xine_config_lookup_entry > > > should be a lot safer. > > > > introducing a mutex here would be even better and much simpler and > > would also solve the concurrent write problems daniel mentioned > > When would this mutex be released? if i remember correctly the idea was to have seperate function calls for that - something like xine_config_[un]lock_entry(...) cheers, guenter -- Smoking is one of the leading causes of statistics. -- Fletcher Knebel |