David Farler <accumula...@icloud.com> writes: > 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 ||
Here's an example that uses Twisted http://stackoverflow.com/a/11729467 javascript client <--> websocket <--> twisted server <--> subprocess Do you want the same but using asyncio module? -- Akira -- https://mail.python.org/mailman/listinfo/python-list
