• 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: WO 5.4, Ajax polling and multi-threading questions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WO 5.4, Ajax polling and multi-threading questions


  • Subject: Re: WO 5.4, Ajax polling and multi-threading questions
  • From: Karthik N <email@hidden>
  • Date: Wed, 18 Feb 2009 06:34:17 -0800

hi mike,
 

please keep threads on the list ...

apologies, when i hit Reply in Gmail i expected the Reply To would to the list!

you're absolutely right  in your understanding of my problem statement.

we have WO applications that we run single-threaded because "somebody told somebody years ago" that EOF would choke in a multi-threaded environment.  

also when i tried to open up multi-threading, i was made to understand that EOF is not thread-safe; EOF is not good at locking and bad things will happen, and hence I need to do the locking myself.

based on what you're describing, it appears that EOF will take care of itself and i don't need to do a thing besides 

-WOAllowsConcurrentRequestHandling YES -WOWorkerThreadCountMax 32

looks like i woke up on the right  side of bed, if that's the case!



the issue is that i need to host the ajax direct actions in a WOA that already has EOF in the picture.  The EOF related calls too are served through existing DAs.

if i just turn on multi-threading and do not synchronize the EOF calls, then if two or more requests came in for EOF related operations they would choke? [is what i understand]
if you're making ajax calls that (as I understood it from your original) are NOT touching eof, you're not going to lock against EOF ... they're just unrelated method calls.  if you have two direct actions touching EOF, then yes, if you are .lock()ing properly, they will become single-threaded at one of the layers of EOF.

so if person A calls dontTouchEOFAction(), person B calls touchEOFAction(), and person C calls touchAnotherPartofEOFAction(), person A will not block or be blocked by anything, person B and C will be single-threaded and one will block the other until the database operation is complete.


ms

_______________________________________________
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

 _______________________________________________
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: WO 5.4, Ajax polling and multi-threading questions
      • From: Mike Schrag <email@hidden>
References: 
 >WO 5.4, Ajax polling and multi-threading questions (From: Karthik N <email@hidden>)
 >Re: WO 5.4, Ajax polling and multi-threading questions (From: Mike Schrag <email@hidden>)
 >Re: WO 5.4, Ajax polling and multi-threading questions (From: Mike Schrag <email@hidden>)

  • Prev by Date: Re: Sproutcore
  • Next by Date: Re: WO 5.4, Ajax polling and multi-threading questions
  • Previous by thread: Re: WO 5.4, Ajax polling and multi-threading questions
  • Next by thread: Re: WO 5.4, Ajax polling and multi-threading questions
  • Index(es):
    • Date
    • Thread