• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Get control of your email attachments. Connect all your Gmail accounts and in less than 2 minutes, Dokkio will automatically organize your file attachments. You can also connect Dokkio to Drive, Dropbox, and Slack. Sign up for free.


WRFS Model Execution Sequence

Page history last edited by PBworks 12 years, 7 months ago

Sample Execution Sequence


"A My Images Folder"



For this particular example, we'll assume the application is a photo slide show that displays all of the user's photos regardless of where they are stored.


  1. User logs into application via openID-type id
  2. Application then queries the "web inode" provider to find all image containers for this particular user
  3. The next step would logically be for each resource container to be checked for permissions (?)
  4. Each resource container then would be queried for either a summary of resources available for that id (a list of image urls) or the actual data itself would be returned (social graph data)
  5. the WRFS Model Stack would then aggregate each "block of data" as it was returned into a complete "recordset" and returned via event handlers to the application layer.




Comments and Notes


  • The model allows for an OSI Network Model - like abstraction, so that application developers do not worry about XFN, SIOC, RDF -- they focus on developing their application, just like when you write a web server you arent worried about implementing TCP, but moreso you simply work with sockets and streams.
  • This model is implementation agnostic. We should clearly define a model, provide a reference implementation for the data providers and the data consumers, but in the end, as long as a "stack" adhered to the protocol, the technology that implements a layer should not be an issue --- its about function, people.
  • This model is very much inspired by not only the filesystem metaphor, but shares many traits with newer distributed filesystems (google FS, Hadoop, Amazon's Dynamo)

Comments (0)

You don't have permission to comment on this page.