9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Shawn Rutledge <lists@ecloud.org>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Vcard filesystem
Date: Thu, 14 Nov 2024 10:27:15 +0100	[thread overview]
Message-ID: <60988E97-98A2-441B-A538-674DCF38B88A@ecloud.org> (raw)
In-Reply-To: <64a162b2-a937-4b06-8035-96295cf11dda@sirjofri.de>

> On Nov 8, 2024, at 17:04, sirjofri <sirjofri+ml-9fans@sirjofri.de> wrote:
> 
> Hello everyone,
> 
> some time ago I started working on a filesystem for vcard files. The filesystem manages a vcard database (stored in the user lib dir), and mounts itself to /mnt/vcard per default.

I don’t think I like the idea of one big vcf file for all contacts.  I’d prefer to use a directory with a file for each contact, where the file name is the person’s name.  That way it’s already easy to use cat and grep on the raw files, and easy to use tools like syncthing to keep the whole database in sync between devices (there’s much less chance of sync conflicts if it’s broken up, and the file timestamp always indicates the last-updated time for a single record.  Yeah, we don’t have syncthing, but I assume you have some way to sync files for offline use.)  The file server should just make each vcard file appear as a directory, and each property becomes a file inside, as you have it already.  It should help with multi-process writing too, only writing to one record at a time in each process.

But it’s good that you have a working parser for the most recent version.


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4d117dbbd00ae4f7-M68e41c1368ca65891193463f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  parent reply	other threads:[~2024-11-14  9:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 16:04 sirjofri
2024-11-13  4:29 ` Noam Preil
2024-11-14  9:27 ` Shawn Rutledge [this message]
2024-11-14 22:13   ` Frank D. Engel, Jr.

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=60988E97-98A2-441B-A538-674DCF38B88A@ecloud.org \
    --to=lists@ecloud.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).