From: "Mathieu L." <lejatorn@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] dial and time out
Date: Thu, 10 Sep 2009 11:32:28 +0200 [thread overview]
Message-ID: <e48ca67a55a6fbe6504fa8cfc08117e3@smgl.fr.eu.org> (raw)
Hello 9fans,
I have a bunch of threads, simply scheduled with yield() at the moment
(I'll use alt later on), and each of them is calling dial() at some
point. I don't want the other threads to wait for "too long" when one
of them is blocked on a dial() that will eventually time out.
So I was thinking, for each of them, of creating a proc which would
be used as a timer; it would be created just before the call to dial,
wait for some time, and then kill the dial()ing thread. And as mechiel
suggested, the dial()ing thread would also be set to kill the timer
after it successfully dialed, hence not being killed if it was fast
enough.
Is that the right way to go? If yes, can anyone think of an already
existing example I can look at?
Mathieu
next reply other threads:[~2009-09-10 9:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 9:32 Mathieu L. [this message]
2009-09-10 9:34 ` erik quanstrom
2009-09-10 9:51 ` Mathieu L.
2009-09-10 9:59 ` erik quanstrom
2009-09-10 10:07 ` Sape Mullender
2009-09-10 9:57 ` Sape Mullender
2009-09-10 11:26 ` Mathieu L.
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=e48ca67a55a6fbe6504fa8cfc08117e3@smgl.fr.eu.org \
--to=lejatorn@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).