On 09/06/2012 07:52 PM, Tom Breton (Tehom) wrote: > I've moved the read lock in MappedEventBuffer::peek into > MappedBufMetaIterator functions so that it covers the entire scope during > which the MappedEvent pointer is exposed. It's not perfect, because > caller has to know to do that, but it's much better than my first > solution.
Thanks, Tom, all this stuff you've been doing looks really good. Would it be possible to make a copy of the event in order to reduce the time that it is locked? Just a random thought. Not sure if making a copy even makes any sense. Just seems like with all the multi-threading stuff I've been reading, it's not uncommon to copy some data to reduce locking periods. I've unfortunately had little opportunity to work with multi-threading. Hoping to get more into it soon. Ted. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
