• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Another concurrency problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Another concurrency problem


  • Subject: Re: Another concurrency problem
  • From: Kieran Kelleher <email@hidden>
  • Date: Wed, 8 Aug 2007 14:38:07 -0400

As long as you use Wonder's ERXObjectStoreCoordinatorSynchronizer class, notifications are all taken care of for you. According to Mike Schrag, this has been well tested under heavy load and I have seen zero issues with it ...... in fact you will have issues if you don't use it.

On Aug 8, 2007, at 1:57 PM, Ken Anderson wrote:


On Aug 7, 2007, at 12:07 PM, Kieran Kelleher wrote:

2) Use a separate ObjectStoreCoordinator for your background thread to avoid locking conflicts

What are the downsides of doing this?  I have to admit, my object store coordinator recollection is sketchy.  Do you have to implement your own method for notifications between coordinators?

Thanks,
Ken

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Another concurrency problem
      • From: John Larson <email@hidden>
    • Re: Another concurrency problem
      • From: Mike Schrag <email@hidden>
References: 
 >Another concurrency problem (From: John Larson <email@hidden>)
 >Re: Another concurrency problem (From: Kieran Kelleher <email@hidden>)
 >Re: Another concurrency problem (From: Ken Anderson <email@hidden>)

  • Prev by Date: Re: Another concurrency problem
  • Next by Date: Re: Another concurrency problem
  • Previous by thread: Re: Another concurrency problem
  • Next by thread: Re: Another concurrency problem
  • Index(es):
    • Date
    • Thread