From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: weigelt@metux.de,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Server management
Date: Thu, 13 Sep 2007 10:10:15 -0500 [thread overview]
Message-ID: <a4e6962a0709130810u23021a3fo89918297c4c1ae10@mail.gmail.com> (raw)
In-Reply-To: <20070913141141.GA11706@nibiru.local>
On 9/13/07, Enrico Weigelt <weigelt@metux.de> wrote:
>
> while thinking about my plans for using 9P servers in numerious
> situations I just realized that server management can become
> quite complex.
>
> For example if an application like mozilla would move out many
> jobs (ie. like currently discussing @ mozilla.org: rss-feeds),
> server management can be quite complicated. We can't expect
> neither the user nor the individual application to be responsible
> for that. We need some zero-configuration approach.
>
> Actually it can be done by another server, which knows about
> all the individual servers, handles startup/shutdown and tells
> the clients where to find them, how to authenticate, etc, etc.
> A little bit like RPC portmap.
>
> What do you think about this idea ?
>
While going with something "standard" (but a bit sticky) like zeroconf
may be attractive, you may want to look at what the Plan B guys did --
IIRC they have network discovery and organization integrated into
their basic framework.
Essentially I think it makes the most sense to work this sort of
auto-discovery into existing services (ndb/cs for instance).
Accomodating zeroconf as a protocol would be nice (particularly from a
cross-platform compatibility angle), but you could also do something
like Inferno's registry.
-eric
next prev parent reply other threads:[~2007-09-13 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 14:11 Enrico Weigelt
2007-09-13 14:33 ` Gabriel Diaz
2007-09-13 15:10 ` Eric Van Hensbergen [this message]
2007-09-13 17:47 ` Francisco J Ballesteros
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=a4e6962a0709130810u23021a3fo89918297c4c1ae10@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=weigelt@metux.de \
/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).