Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #73584 > unrolled thread

asyncio: wrapping a subprocess in a server

Started byDavid Farler <accumulator@icloud.com>
First post2014-06-25 11:24 -0700
Last post2014-06-25 11:24 -0700
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python


Contents

  asyncio: wrapping a subprocess in a server David Farler <accumulator@icloud.com> - 2014-06-25 11:24 -0700

#73584 — asyncio: wrapping a subprocess in a server

FromDavid Farler <accumulator@icloud.com>
Date2014-06-25 11:24 -0700
Subjectasyncio: wrapping a subprocess in a server
Message-ID<mailman.11239.1403721083.18130.python-list@python.org>

[Multipart message — attachments visible in raw view] — view raw

Hi all,

I'm trying to vend some kind of server that spawns a client-unique subprocess when a client connects. The server acts as a middleman, receiving structure messages from the client, sending input to the subprocess, and packaging up subprocess data before sending back to the client. The connection is long-lived and the client can continue to send "requests". If the subprocess crashes or dies, the server should be able to revive it transparently.

I know how to separately create server and subprocess protocols and having the event loop run either until completion, but what is the best way to chain two protocols together?

|| Client || <~~ TCP ~~> || Server <--> Subprocess ||

Regards,
David

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web