From: "Jeroen Frijters" <jeroen@sumatra.nl>
To: "Casey Marshall" <csm@gnu.org>
Cc: <mauve-discuss@sourceware.org>
Subject: RE: New SocketChannel test that requires testing
Date: Wed, 20 Sep 2006 04:34:00 -0000 [thread overview]
Message-ID: <D92197D0A6547B44A1567814F851FA6827A9BD@LEMBU.sumatrasoftware.com> (raw)
In-Reply-To: <45103899.7070400@gnu.org>
Casey Marshall wrote:
> > I don't think it has nothing to do with the underlying
> > socket mechanics,
> > it is simply an invariant of the SocketChannel API.
>
> Nope:
>
> "If this channel is in non-blocking mode then an invocation of this
> method initiates a non-blocking connection operation. If the
> connection is established immediately, as can happen with a local
> connection, then this method returns true. Otherwise this method
> returns false and the connection operation must later be completed
> by invoking the finishConnect method." [1]
>
> 1.
> http://java.sun.com/j2se/1.4.2/docs/api/java/nio/channels/Sock
> etChannel.html#connect(java.net.SocketAddress)
May be I misunderstood what you meant, we were talking about
isConnected() changing its return value right? The only way I can read
the text you quoted is that it confirms that isConnected() will only
return true iff either connect() or finishConnect() previously returned
true.
Regards,
Jeroen
next prev parent reply other threads:[~2006-09-20 4:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 11:30 Jeroen Frijters
2006-09-18 22:45 ` Casey Marshall
2006-09-19 5:32 ` Jeroen Frijters
2006-09-19 8:08 ` Casey Marshall
2006-09-19 8:21 ` Jeroen Frijters
2006-09-19 18:36 ` Casey Marshall
2006-09-20 4:34 ` Jeroen Frijters [this message]
2006-09-20 5:14 ` Casey Marshall
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=D92197D0A6547B44A1567814F851FA6827A9BD@LEMBU.sumatrasoftware.com \
--to=jeroen@sumatra.nl \
--cc=csm@gnu.org \
--cc=mauve-discuss@sourceware.org \
/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).