From: sqweek <sqweek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Storing bookmarks+history w/ 9P
Date: Mon, 3 Dec 2007 17:08:10 +0900 [thread overview]
Message-ID: <140e7ec30712030008u4bbcdf1fybc1474c999b72cf6@mail.gmail.com> (raw)
In-Reply-To: <20071130045601.GB2817@nibiru.local>
On Nov 30, 2007 1:56 PM, Enrico Weigelt <weigelt@metux.de> wrote:
> I already wrote some ideas for storing browser bookmarks and
> history via an synthetic filesystem some time ago.
>
> Here's a little wiki page about this:
>
> http://oss-qm.metux.de/index.php/9forge/bookmarkfs
Hm. My knowledge of 9P is worse than I would like, so I don't have a
good idea of what makes sense to implement. Nor do I have a lot of
experience with synthetic file servers to know what works and what
doesn't. But, I suspect you're focusing a bit too much on existing
interface, rather than simplicity and the "right" approach.
Putting a .bookmark extension on every file seems excessive for an fs
that essentially only contains directories and bookmarks. Also, the
actual filename doesn't appear to be used for anything - so judging by
Mozilla's past, if such an interface is adopted by Gecko you'll get
B84E21AC.bookmark, A8BF4371.bookmark, etc etc.
What if the filename corresponded to the bookmark name, and do you
really need a description field? If you dropped it, you'd have
filename <=> bookmark name, mtime <=> last visited, file contents <=>
url. It maps better to history entries also, which certainly don't
have descriptions. /history/by-proto-date-hostname/date essentially
corresponds to an "ls -rt /history",
/history/by-proto-date-hostname/hostname is just "cat /history/*
|sort". Though considering how many entries you'll have, I wonder if a
file per history entry is even a sensible approach here. A flat file
with two columns(DATE HOSTNAME) does pretty much the same job with
less overhead/clutter...
-sqweek
next prev parent reply other threads:[~2007-12-03 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 4:56 Enrico Weigelt
2007-12-03 8:08 ` sqweek [this message]
2007-12-05 11:02 ` Enrico Weigelt
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=140e7ec30712030008u4bbcdf1fybc1474c999b72cf6@mail.gmail.com \
--to=sqweek@gmail.com \
--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).