anchor.diff:  and does some transformations along the way.
   
   Currently, the mapping is very straightforward: the path +/assets/123abc/css/style.less+ is mapped to resource
  -+META-INF/assets/css/style.less+ and transformed from Less to CSS along the way.
  -Embedded in the middle is the content checksum for the file (+123abc+).
  ++META-INF/assets/css/style.less+ which is read into memory and transformed from Less to CSS.
  +Embedded in the middle of the URL is the content checksum for the file (+123abc+).
   
   In your application, assets will change during development, or between production deployments. The URIs provided to
   the client agent (the web browser) is a _resource_; resources are immutable.
  
positive.code: 
  The +:content-types+ key maps file extensions to MIME types.
  
  The +:compressable+ key identifies which content types are compressable; note the use of the +/*+ suffix to indicate
  that all text content types are compressable.
  
  File system caching is normally only enabled in development mode.
  
  Twixt always caches the content of files in memory, after any transforming operations (such as compiling CoffeeScript to
  JavaScript). 
  In development mode, checks are enabled to refresh the cache when underlying files are modified; 
  in production, no such checks occur as it is assumed that all such assets are stable
  (until the entire application is re-deployed).
  
negative.code: The checksum has a optional "z" prefix; this indicates a GZip compressed resource.
  Twixt detects if the client agent supports GZip compression (via the +Accept-Encodings+ header).
  In addition, compression is only applied to specific content types, such as "text/html" and "application/edn".
  Most binary formats, including fonts and images, are already compressed.
  
  Because of this, when referencing assets inside your templates, you must pass paths (relative to +META-INF/assets+)
  through Twixt to get URIs that will work in the browser:
  