From: "Boehm, Hans" <hans_boehm@hp.com>
To: "'Miles Sabin'" <msabin@cromwellmedia.co.uk>,
"'java-discuss@sourceware.cygnus.com'"
<java-discuss@sourceware.cygnus.com>
Subject: RE: Thread.interrupt()
Date: Wed, 15 Mar 2000 13:52:00 -0000 [thread overview]
Message-ID: <140D21516EC2D3119EE700902787664456E703@hplex1.hpl.hp.com> (raw)
Miles Sabin wrote:
>Boehm, Hans wrote,
>> In the case of resource invocation, there is no defined
>> protocol, and thus essentially no libraries that abide by it.
>Well, there is, sort of.
>Resource revocation implies that the current or next use of
>the resource will fail. That should result in an exception
>throw (an IOException in this particular case). In general I
>would expect well behaved libraries to respond gracefully in
>the face of such an event.
That's not the issue. The problem is that with resource revocation
there is no standard method that thread A would call to terminate B.
Equivalently, there is no protocol that would allow thread A to locate
the resource it should revoke to terminate thread B. I haven't a clue how
to terminate a thread that might hang during name lookup in a standard
library if I'm constrained to use resource revocation.
Hans
WARNING: multiple messages have this Message-ID
From: "Boehm, Hans" <hans_boehm@hp.com>
To: "'Miles Sabin'" <msabin@cromwellmedia.co.uk>,
"'java-discuss@sourceware.cygnus.com'"
<java-discuss@sourceware.cygnus.com>
Subject: RE: Thread.interrupt()
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <140D21516EC2D3119EE700902787664456E703@hplex1.hpl.hp.com> (raw)
Message-ID: <20000401000000.nP0Z_rr23MY6Oa5jF6sQdqJelJUuNFcwCKQJ_VsvwmU@z> (raw)
Miles Sabin wrote:
>Boehm, Hans wrote,
>> In the case of resource invocation, there is no defined
>> protocol, and thus essentially no libraries that abide by it.
>Well, there is, sort of.
>Resource revocation implies that the current or next use of
>the resource will fail. That should result in an exception
>throw (an IOException in this particular case). In general I
>would expect well behaved libraries to respond gracefully in
>the face of such an event.
That's not the issue. The problem is that with resource revocation
there is no standard method that thread A would call to terminate B.
Equivalently, there is no protocol that would allow thread A to locate
the resource it should revoke to terminate thread B. I haven't a clue how
to terminate a thread that might hang during name lookup in a standard
library if I'm constrained to use resource revocation.
Hans
next reply other threads:[~2000-03-15 13:52 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-15 13:52 Boehm, Hans [this message]
2000-04-01 0:00 ` Thread.interrupt() Boehm, Hans
-- strict thread matches above, loose matches on Subject: below --
2000-04-01 0:00 Thread.interrupt() Bryce McKinlay
2000-03-13 13:33 ` Thread.interrupt() Bryce McKinlay
2000-03-14 2:24 ` Thread.interrupt() Kresten Krab Thorup
2000-03-14 3:26 ` Thread.interrupt() Bryce McKinlay
2000-04-01 0:00 ` Thread.interrupt() Bryce McKinlay
2000-03-14 5:52 ` Thread.interrupt() Jeff Sturm
2000-03-14 11:02 ` Thread.interrupt() Tom Tromey
2000-04-01 0:00 ` Thread.interrupt() Tom Tromey
2000-03-14 14:16 ` Thread.interrupt() Bryce McKinlay
2000-03-14 16:09 ` Thread.interrupt() Godmar Back
2000-04-01 0:00 ` Thread.interrupt() Godmar Back
2000-04-01 0:00 ` Thread.interrupt() Bryce McKinlay
2000-04-01 0:00 ` Thread.interrupt() Jeff Sturm
2000-04-01 0:00 ` Thread.interrupt() Kresten Krab Thorup
2000-04-01 0:00 ` Thread.interrupt() Bryce McKinlay
2000-03-16 4:08 Thread.interrupt() Miles Sabin
2000-04-01 0:00 ` Thread.interrupt() Miles Sabin
2000-03-15 13:06 Thread.interrupt() Miles Sabin
2000-04-01 0:00 ` Thread.interrupt() Miles Sabin
2000-03-15 12:55 Thread.interrupt() Boehm, Hans
2000-04-01 0:00 ` Thread.interrupt() Boehm, Hans
2000-03-15 11:57 Thread.interrupt() Miles Sabin
2000-04-01 0:00 ` Thread.interrupt() Miles Sabin
2000-03-15 11:38 Thread.interrupt() Boehm, Hans
2000-04-01 0:00 ` Thread.interrupt() Boehm, Hans
2000-03-15 5:51 Thread.interrupt() Miles Sabin
2000-04-01 0:00 ` Thread.interrupt() Miles Sabin
2000-03-14 16:30 Thread.interrupt() Boehm, Hans
2000-03-14 17:17 ` Thread.interrupt() Jesper Peterson
2000-03-14 17:27 ` Thread.interrupt() Tom Tromey
2000-04-01 0:00 ` Thread.interrupt() Tom Tromey
2000-04-01 0:00 ` Thread.interrupt() Jesper Peterson
2000-04-01 0:00 ` Thread.interrupt() Boehm, Hans
2000-03-14 11:26 Thread.interrupt() Boehm, Hans
2000-04-01 0:00 ` Thread.interrupt() Boehm, Hans
2000-03-14 9:57 Thread.interrupt() Boehm, Hans
2000-03-14 10:52 ` Thread.interrupt() Tom Tromey
2000-04-01 0:00 ` Thread.interrupt() Tom Tromey
2000-03-14 15:59 ` Thread.interrupt() Jesper Peterson
2000-04-01 0:00 ` Thread.interrupt() Jesper Peterson
2000-04-01 0:00 ` Thread.interrupt() Boehm, Hans
2000-03-14 7:47 Thread.interrupt() Miles Sabin
2000-04-01 0:00 ` Thread.interrupt() Miles Sabin
2000-03-14 6:00 Thread.interrupt() Miles Sabin
2000-03-14 7:36 ` Thread.interrupt() Jeff Sturm
2000-03-14 10:58 ` Thread.interrupt() Tom Tromey
2000-04-01 0:00 ` Thread.interrupt() Tom Tromey
2000-04-01 0:00 ` Thread.interrupt() Jeff Sturm
2000-04-01 0:00 ` Thread.interrupt() Miles Sabin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=140D21516EC2D3119EE700902787664456E703@hplex1.hpl.hp.com \
--to=hans_boehm@hp.com \
--cc=java-discuss@sourceware.cygnus.com \
--cc=msabin@cromwellmedia.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).