From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Interested in improving networking in Plan 9
Date: Mon, 31 Aug 2009 16:55:44 +0200 [thread overview]
Message-ID: <8ccc8ba40908310755q76c52917qa8483db5ed2aa9bc@mail.gmail.com> (raw)
In-Reply-To: <a4e6962a0908310725k2de9b87dl92c12b3105ddb189@mail.gmail.com>
Hmmm. we did that for FS processes on Plan B. I mean, keep a
dynamic version of a registry. It kept the list of volumes available at a
central place.
I think it can be used as is on Plan 9, without changes.
There was a program (I think it was called adsrv; not sure, it´s on the
Plan B man pages) were file servers could keep an open file as long as
they were alive.
We didn´t do load balancing but it shouldn´t be hard to add that to
this program.
If there´s interest I can dig in our worm (although it should be also
on sources).
On Mon, Aug 31, 2009 at 4:25 PM, Eric Van Hensbergen<ericvh@gmail.com> wrote:
> On Mon, Aug 31, 2009 at 9:04 AM, erik quanstrom<quanstro@quanstro.net> wrote:
>>
>> given the database= option, if one could confine rapid changes to
>> smaller files, one could teach ndb to only reread changed files.
>>
>
> Why not have a synthetic file system interface to ndb that allows it
> to update its own files? I think this is my primary problem.
> Granular modification to static files is a PITA to manage -- we should
> be using synthetic file system interfaces to to help manage and gate
> modifications. Most of the services I have in mind may be transient
> and task specific, so there are elements of scope to consider and you
> may not want to write anything out to static storage.
>
>>> registration/discovery mechanism to existing applications. When I
>>> export, a flag should make that export visible to zeroconf resolution,
>>> etc.
>>
>> what do you mean by export?
>>
>
> When I publish a service, in the Plan 9 case primarily by exporting a
> synthetic file system. I shouldn't have to have static configuration
> for file servers, it should be much more fluid. I'm not arguing for a
> microsoft style registry -- but the network discovery environment on
> MacOSX is much nicer than what we have today within Plan 9. An even
> better example is the environment on the OLPC, where many of the
> applications are implicitly networked and share resources based on
> Zeroconf pub/sub interfaces.
>
> -eric
>
>
next prev parent reply other threads:[~2009-08-31 14:55 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 7:21 Vinu Rajashekhar
2009-08-30 14:21 ` ron minnich
2009-08-30 16:19 ` Eric Van Hensbergen
2009-08-30 17:07 ` erik quanstrom
2009-08-30 17:40 ` Venkatesh Srinivas
2009-08-30 17:53 ` erik quanstrom
[not found] ` <c81a07350908300842w3df8321aidf55096b65eb9b77@mail.gmail.com>
2009-08-30 18:17 ` ron minnich
2009-08-30 18:35 ` ron minnich
2009-08-31 3:34 ` erik quanstrom
2009-08-31 12:45 ` Eric Van Hensbergen
2009-08-31 12:51 ` erik quanstrom
2009-08-31 12:59 ` Vinu Rajashekhar
2009-08-31 13:05 ` erik quanstrom
2009-08-31 13:48 ` Anthony Sorace
2009-08-31 14:51 ` Devon H. O'Dell
2009-08-31 15:03 ` Vinu Rajashekhar
2009-08-31 13:42 ` Eric Van Hensbergen
2009-08-31 14:04 ` erik quanstrom
2009-08-31 14:25 ` Eric Van Hensbergen
2009-08-31 14:36 ` erik quanstrom
2009-08-31 14:57 ` Eric Van Hensbergen
2009-08-31 15:52 ` erik quanstrom
2009-08-31 16:12 ` Eric Van Hensbergen
2009-08-31 14:55 ` Francisco J Ballesteros [this message]
2009-08-31 15:09 ` Eric Van Hensbergen
2009-08-31 15:56 ` erik quanstrom
2009-08-31 16:16 ` Bakul Shah
2009-08-31 16:33 ` Eric Van Hensbergen
2009-09-02 16:50 ` Bakul Shah
2009-09-02 17:10 ` Robert Raschke
2009-09-03 11:21 ` matt
2009-09-03 12:50 ` erik quanstrom
2009-09-03 16:13 ` Anthony Sorace
2009-09-03 16:29 ` erik quanstrom
2009-09-03 16:34 ` Robert Raschke
2009-09-03 21:50 ` Daniel Lyons
2009-09-03 19:08 ` Steve Simon
2009-08-31 17:09 ` Devon H. O'Dell
2009-08-31 17:20 ` erik quanstrom
2009-08-31 17:32 ` Devon H. O'Dell
2009-08-31 18:00 ` erik quanstrom
2009-08-31 4:17 ` Federico G. Benavento
2009-08-31 4:53 ` Vinu Rajashekhar
2009-08-30 17:22 erik quanstrom
2009-08-30 17:36 ` Vinu Rajashekhar
2009-08-30 17:56 ` erik quanstrom
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=8ccc8ba40908310755q76c52917qa8483db5ed2aa9bc@mail.gmail.com \
--to=nemo@lsub.org \
--cc=9fans@9fans.net \
/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).