Classic Note Entries

Ideas from TiddlyWeb

These ideas came from ~TiddlyWeb

When writing code separate,

  • web request handling (wsgi, maki)
  • data model (the content model , tiddler, image, etc.)
  • serialization model (format of the content model, xml, html, txt, json, etc.)(has to work both ways!)
  • storage model (on the filesystem AND in Zebra AND OR dbxml with webdav)
  • authentication model (simple http)
  • authorization model. (? policy thingy (role, owner, etc.))

In each distinct section ask what are the resources and what are the simple REST-like actions that will be performed. Minimize state. Maximize separation and layers.

Types from TiddlyWeb

  • store
  • serializer
  • handler
  • challenger (authentication)
  • extractor (authentication)
  • validator (called when resources are put)
  • filter
  • renderer