From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <6e8f08c5154b407b89788761ff5992c0@plan9.bell-labs.com> To: 9fans@cse.psu.edu Subject: Re: [9fans] aan documentation From: Peter Bosch In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Sun, 2 Mar 2003 12:13:55 -0500 Topicbox-Message-UUID: 769d0a18-eacb-11e9-9e20-41e7f4b1d025 >> The manpage for aan says it uses a unique protocol. Is >> its operation described anywhere (other than the source)? > > read the source, luke. ok, that was too quick. here's how it works. Aan (Always Available Network) sits on both client and server and it reads from stdin and writes to stdout on both ends. internally, aan keeps state of the bytes that have been exchanged between client and server and it acknowledges the reception of data on each message that is exchanged between the client and server (bi-directional). in case a (TCP) connection breaks, aan restablishes contact from the client to the server -- the server listens on a private port for each established connection. if the server does not hear from a client within a timeout (currently a 24 hours), it cleans up state on the server side. aan assumes the data that it ships to be encrypted. the idea is that you can suspend your notebook without your 9P connections to die. peter.