Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: BroadcastingDispatcher bug

  1. #11
    Join Date
    May 2007
    Location
    Netherlands
    Posts
    614

    Default

    please take a look at this code and reopen the issue if you think there's something off with it.

    https://fisheye.springsource.org/bro...2=2366&r1=2279

  2. #12
    Join Date
    Oct 2005
    Location
    Boston, MA
    Posts
    2,840

    Default

    I just made a few minor changes:
    https://fisheye.springsource.org/cha...ation/?cs=2367

    However, we might be able to push down all locking into the underlying OrderedAwareLinkedHashSet implementation. At this point, the only relevant methods lacking a lock there are toArray().

    -Mark

  3. #13
    Join Date
    Oct 2005
    Location
    Boston, MA
    Posts
    2,840

    Default

    Dan,

    Have a look at the most recent changes:
    https://fisheye.springsource.org/cha...ation/?cs=2368

    All concurrent access safety is being managed within the OrderedAwareLinkedHashSet implementation now. Let me know what you think, and if you have time to bombard that collection with some similar tests, that would be really helpful.

    Regards,
    Mark

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •