Path: csiph.com!usenet.pasdenom.info!news.redatomik.org!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <CACvLUangsktYPpG2gkW6yr-3zq+=t-Nkfefo6tnOU4bQX2Q++A@mail.gmail.com>
References: <CACvLUangsktYPpG2gkW6yr-3zq+=t-Nkfefo6tnOU4bQX2Q++A@mail.gmail.com>
From: Ian Kelly <ian.g.kelly@gmail.com>
Date: Fri, 3 Jul 2015 08:31:15 -0600
Subject: Re: An asyncio example
To: Python <python-list@python.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.273.1435933923.3674.python-list@python.org>
Lines: 39
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:93463

On Fri, Jul 3, 2015 at 4:28 AM, Adam Barto=C5=A1 <drekin@gmail.com> wrote:
> Hello,
>
> I'm experimenting with asyncio. I have composed the following code. There=
 is
> a server handler and a client handler. I didn't want to split the code in=
to
> two files so I just used a socketpair, inspired by example
> https://docs.python.org/3/library/asyncio-stream.html#register-an-open-so=
cket-to-wait-for-data-using-streams
> . However, my code doesn't work =E2=80=93 it blocks because both sides ar=
e trying to
> read more data. But if I close the writer on one side (the commented line=
),
> whole connection is closed. So
>
> 1) is there a way to close just one direction of the connection?

No. SOCK_STREAM sockets are always bidirectional.

> 2) In the blocked situaction even KeyboardInterrupt doesn't break the loo=
p,
> is that desired behavior? And why?

I don't think so. When I tried this locally (using Python 3.4.0, so
replacing "async def" with "def" and "await" with "yield from" and
"loop.create_task" with "asyncio.async") pressing Ctrl-C did interrupt
the loop.

> 3) Are there some other issues with my code with respect to =E2=80=9Cbest=
 practices=E2=80=9D
> how to write a code like this?

There are a couple of approaches you could take. Since your protocol
is so far text-based, I would suggest adding '\n' to the ends of your
messages and using reader.readline instead of reader.read.
Alternatively, since the writer isn't planning to write anything
further after its one message, just call writer.write_eof() (not
writer.close) after the call to write.