Build a Web 2.0-like application in haskell, with HAppS.
happstutorial.com
happstutorial.com
Nothing kills the urge to learn something quicker than incomplete docs. But it doesn't have to be this way. John Resig of JDoc fame, gets around this problem by concentrating on writing good documentation of the core API ~ http://blog.jquery.com/2006/09/02/taking-jquery-documentatio... (along with doing stacks of talks, demos) leaving the gaps for others to fill ~ http://www.html.it/articoli/johnresig/index.html
It's not really a "minor detail."
There's a "getting organized" thread on the happs googlegroup about this at the moment, and I really hope it bears fruit.
This should be done via haddock of course, but haddock won't build HAppS documentation at the moment because it doesn't work with template haskell (as discussed in the googlegroup). Optimistically, this should be working again after ghc 6.10.2, which also targets a haddock fix.
Even without working haddock though, the api should be better documented in the source. If haddock suddenly started working there still would be a lot of undocumented functions.
But how ever solid one might think one's app is, there's no reason not to make one's front page static or at least have apache cache it.
So yeah, load test and do whatever it takes to ensure you're ready for traffic.
http://groups.google.com/group/HAppS/browse_thread/thread/cf...
Basically it was a lazy io issue in haskell, fix was using a strict version of readFile for templates.
Hope it stays up now!
Meanwhile I restarted the server and it's running again.
There are new chapters on various macid topics, utf8 gotchas, cookies, and various improvements all over.
Please continue to report errors and inconsistencies as they come up.
This version is "close to final". At least for my purposes, it has boilerplate that covers nearly all the important important use cases for a web 2.0 app. OK I missed a few -- eg, there's still no email confirmation with registration -- but there's a hell of a lot.
So... don't use ruby for your next web 2.0 app -- use haskell!
thomas.