• 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: Deadlocks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Deadlocks


  • Subject: Re: Deadlocks
  • From: "Matthew W. Taylor" <email@hidden>
  • Date: Wed, 05 Sep 2007 20:47:02 -0500
  • Thread-topic: Deadlocks

"If virtue
can't be mine alone
at least my faults
can be my own."
    - Piet Hein

Deadlocks in WebObjects have always been my own fault.  I'm thankful to
Andrew Lindesay's HOWTO.  It's a super easy process -- and saves my bacon
from my own carelessness.

> From: Steven Mark McCraw <email@hidden>
> Date: Wed, 5 Sep 2007 20:22:42 -0400
> To: Chuck Hill <email@hidden>
> Cc: "WebObjects (Group)" <email@hidden>
> Subject: Re: Deadlocks
>
>> Is it easy?  Or is that just the nature of the concurrency beast?
>
> I consider it easy because I've had to deal with it so many times.  I
> think WebObjects seems worse than a normal multithreaded app because
> things you do that are totally unrelated to concurrency from the
> programmer's point of view can cause you deadlock.

Deadlocks sure are frustrating. In my opinion WO locks are only more
noticeable than other web app environments, because, in classical WO
programming, you've only got one channel to the DB per application. Lock
that up -- and the rest of the app is toast.  Other programming environments
might suffer less by having more avenues to the data.  You might be equally
guilty of poor practice in those environments but possibly not even notice
it. Instead you reboot your app when it slows to a crawl, or runs out of
descriptors, blaming it on Java.

> It's nice that so
> much of the concurrency-handling misery you would ordinarily have to
> think about with multithreaded applications is hidden from you, but
> when it goes wrong, it is the height of confusion.

Well when we see that copy of open-source WO, "Real Soon Now (tm)." we can
all say  what confusion?

-=- matt

Matthew Taylor
Northwestern University

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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: Deadlocks
      • From: Chuck Hill <email@hidden>
References: 
 >Re: Deadlocks (From: Steven Mark McCraw <email@hidden>)

  • Prev by Date: Re: Deadlocks
  • Next by Date: Re: Deadlocks
  • Previous by thread: Re: Deadlocks
  • Next by thread: Re: Deadlocks
  • Index(es):
    • Date
    • Thread