9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: matt <mattmobile@proweb.co.uk>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] dbfs and web framework for plan 9
Date: Mon, 24 Nov 2008 10:58:37 +0000	[thread overview]
Message-ID: <492A88DD.2070900@proweb.co.uk> (raw)
In-Reply-To: <20081123220653.GA25062@nibiru.local>


> That's exactly what constraints, rules in SQL etc are for.
> Maybe some similar ruling system for filesystems would be fine :)
> (any suggestions ?)
>
That's what I was driving at. To map SQL <> FS you end up replicating
lots of SQL logic in your client FS. Reads are *always* out of date.
Writes can happen across tables but need to be atomic and able to roll back.

Funny you should mention rules for filesystems. I also did the opposite
and wrote a front end that mapped 9p onto SQL. I.E. a scehma that
represented a file system with QIDs etc. with a python marshaller
inbetween such that Postgres was the backing store for 9p.

I got a bit stuck when the file sizes got over the row size, the blob
spec wasn't very clearly documented to me; all you get is the C function
definitions rather than what goes over the wire so it's another project
in the unfinished pile :)

I've got a few weeks off soon and I'm going to revisit my py9p :)





  parent reply	other threads:[~2008-11-24 10:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23 18:58 [9fans] dbfs and web framework for plan 9 (was: web-based plan 9?) Giacomo Tesio
2008-11-23 22:06 ` Enrico Weigelt
2008-11-23 22:26   ` Francisco J Ballesteros
2008-11-23 22:50     ` Enrico Weigelt
2008-11-24  9:27   ` Giacomo Tesio
2008-11-24  9:30     ` Giacomo Tesio
2008-11-24 10:58   ` matt [this message]
2008-11-24 14:13     ` [9fans] dbfs and web framework for plan 9 Giacomo Tesio

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=492A88DD.2070900@proweb.co.uk \
    --to=mattmobile@proweb.co.uk \
    --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).