From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sun, 1 Jul 2007 05:04:17 -0400 From: Kris Maglione To: 9fans@cse.psu.edu Subject: Re: [9fans] URI scheme for 9P2000 resources Message-ID: <20070701090417.GY28917@kris.home> References: <5d375e920706301326j6efe8921td46d6958299eef62@mail.gmail.com> <20070630225955.GW28917@kris.home> <84d462a30706302313r5bf288c9l43d02fd9b031ddbd@mail.gmail.com> <20070701062425.GX28917@kris.home> <46876BC5.9060802@proweb.co.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kdyvsFMDMDKuFgXB" Content-Disposition: inline In-Reply-To: <46876BC5.9060802@proweb.co.uk> User-Agent: Mutt/1.5.15 (2007-04-06) Topicbox-Message-UUID: 8da90c6e-ead2-11e9-9d60-3106f5b1d025 --kdyvsFMDMDKuFgXB Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 01, 2007 at 09:54:29AM +0100, matt wrote: > The problem I forsee is clunks, unless you keep the 9p alive until the=20 > browser closes you'll have to time them out which is a subject we've touc= h=20 > in recently elsewhere. I don't see how it's relevant. The connections to the server=20 should probably be handled in whatever way FTP connections are=20 handled. Clunks should be handled in the exact same way that=20 closes are (they're equivalent). When the connection closes, the=20 server should automatically handle clunks, regardless. The=20 browser should obviously close the connection before it closes. --=20 Kris Maglione The longer you wait in line, the greater the likelihood that you are standing in the wrong line. --kdyvsFMDMDKuFgXB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQFGh24RseQZD8Aui4wRAg6oAKCAQZ0Kc1cyp4dQDrBgWJbI6D0woQCdGbDh kobPXi/WnBCGJJ/3DkbF7Bc= =e0se -----END PGP SIGNATURE----- --kdyvsFMDMDKuFgXB--