From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] magic loopback
Date: Wed, 20 Sep 2006 11:55:02 +0200 [thread overview]
Message-ID: <9bbc6e976701a7b6302154472335b25e@lsub.org> (raw)
: > the many clients who open /srv/your-service), posting
: > to /srv is dramatically less useful than announcing a
: > network address: there's no way to keep clients separate.
There is. You could use a different file for each client, e.g., like
done with consoles. Perhaps not the thing to do for venti, but
IMHO it could work well for other programs. (I hope, we are
using just that for the new omero :).
next reply other threads:[~2006-09-20 9:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 9:55 Fco. J. Ballesteros [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-17 20:02 erik quanstrom
2006-09-18 3:18 ` erik quanstrom
2006-09-18 8:56 ` Richard Miller
2006-09-18 23:16 ` erik quanstrom
2006-09-19 8:04 ` Richard Miller
2006-09-19 23:07 ` erik quanstrom
2006-09-19 23:25 ` Russ Cox
2006-09-19 23:36 ` erik quanstrom
2006-09-20 0:54 ` Russ Cox
2006-09-20 9:48 ` Charles Forsyth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9bbc6e976701a7b6302154472335b25e@lsub.org \
--to=nemo@lsub.org \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).