anchor.diff:  directing the client to the correct resource (with the correct checksum). 
   This is an extremely unlikely scenario that would involve a running client in a race with a redeployed application.
   
  -=== Direct asset URLs
  +== Direct asset URLs
   
   Sometimes it is not possible to determine the full asset URL ahead of time; a common example would be a client-side
   framework, such as http://angularjs.org[AngularJS] that wants to load HTML templates dynamically, at runtime.
  
positive.code: Twixt's exception report captures all of this and presents it as readable HTML.
  The exception report page also does a decent job of de-mangling Java class names to Clojure namespaces and function names.
  
  === How does Twixt differ from Dieter?
  
  On the application I was building, I had a requirement to deploy as a JAR; Dieter expects all the assets to be on the filesystem; I spent some time attempting to hack the Dieter code to allow resources on the classpath as well.
  When that proved unsuccessful, I decided to build out something a bit more ambitious, that would support the features that have accumulated in Tapestry over the last few years.
  
negative.code: code to see how to configure Twixt options, assemble the Twixt asset pipeline, and finally, provide the necessary
  Ring middleware.
  
  == A question of URLs
  
  At its core, Twixt is a set of Ring middleware that maps certain URL patterns to matching files on the classpath,
  and does some transformations along the way.
  