January 5, 2014
At the end of last year I had some fun implementing a CRDT. These are data structures designed to combine together when you have no control over order of changes, timing of changes, or the number of participants in the data structure. The example I looked at was a sequential datatype, namely the WOOT CRDT for collaborative text editing.
Before you do that, you might want to watch my colleague Noel's talk on Reconciling Eventually-Consistent Data with CRDTs which was, not coincidently, right before mine.
If you find yourself looking at a network and thinking "how can I reliably combine these things?" without global synchronised clocks, do have a look at CRDTs because they are #fun and #interesting.
July 24, 2013
Most of my writing effort has gone into The Lift Cookbook, and one thing I missed was why you might be interested in Lift.
That's now fixed, via a three-part series of short posts over at programming.oreilly.com:
Hope you find the framework as fun and productive as I do.
The Lift Cookbook in PDF, on Kindle, print, via the Play Bookstore, and in iBooks.
February 6, 2013
If you need to resolve DTDs locally with the
scala.xmlparser, you should provide a
This works out because
org.xml.sax.helpers.DefaultHandler, and this gives you the default no-op implementations of
I figured this out from related questions and answers on Stackoverflow.