On Thu, Feb 4, 2010 at 5:40 AM, Rick McGuire <object.r...@gmail.com> wrote:
> There's one additional thing we might consider implementing here. The > waiting activities queue is implemented using a linked list where the > link fields are directly contained within the activity object. This > causes problems if there is a reentrant situation that can cause the > same activity to be added to the queue more than once. When that > happens, it's guaranteed bad day. The changes you have proposed can > step around the problem, but won't really close all of the holes where > this situation might occur. It might not be a bad idea to replace > that linked list with a std collection object for managing the > activity queue. With that situation, it doesn't really matter if the > recursion occurs. The internal control blocks will allow an activity > to be queued up multiple times without causing a problem. This > *should* be a simple change....ignoring for the moment all of the > problems I had the last time I tried to use a std collection class :-) That sounds good too. Especially if there were some other cases where an external function on an attached thread needed to be reentrant. -- Mark Miesfeld ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
