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?

Advertisements

3 Responses to “current design for Context’s virtual filesystem”

  1. John Dougan Says:

    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/

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: