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: * CSS Minification
  * Aggregated JavaScript stacks
  * Aggregated CSS stacks
  * RequireJS support and AMD modules
  * Break out the the Less, Jade, CoffeeScript, and exception reporting support into a-la-carte modules
  
  === Stability
  