current design for Context’s virtual filesystem
I’m writing Context’s virtual filesystem support now. The directory structure looks like this:
--
root
classes
<each class>
methods
all
<each method>
literals
<literal objects>
source
version
inherited
<inherited methods>
local
<locally-defined methods>
slots
all
<each slot>
<instances ordered by slot>
references
<referring objects>
slots
<etc>
inherited
<etc>
local
<etc>
processes
<each process' suspended context>
method
instructions
literals
<literal objects>
sender
<etc>
README.html
--
What do you think?
20 January 2014 at 7:54 am
Any room there for a machine readable version of README.html? Any parseable format (xml/json/sexpr/literal arrays/etc.) will be useful to check versions and compatibility.
BTW, have you ever looked at how various Plan 9 apps use the filesystem for IPC? For example the acme editor/environment: http://doc.cat-v.org/plan_9/4th_edition/papers/acme/
LikeLike
20 January 2014 at 11:42 pm
Good idea, I’ll do that. Maybe just have a separate “version” file with useful JSON stuff in it.
LikeLike
20 January 2014 at 11:45 pm
I spoke with Noah Evans at FOSDEM last year and got an earful about Plan 9, too. Cool.
LikeLike