On 05/06/2008, at 5:31 PM, apfelmus wrote:
WASH/CGI has something in that direction. I don't know a short introduction, but have a look at sections 4 and 8 of the implementation notes
http://www.informatik.uni-freiburg.de/~thiemann/WASH/draft.pdf
I think there is also some work done about using Arrows for this problem, cf John Hughes' original paper. (I hear the use of Arrows was inessential, see the followup by Thiemann.) IMH-and-probably-offtopic-O, the continuation-based approach is semantically nice but I don't think anyone has reconciled it with the general desire for clean and tidy URIs. Going to: http://example.com/continuations/45345345 is not anywhere near as aesthetic / phishing proof / ... as going to e.g. http://example.com/comments/edit/16 (Though I grant that hpaste URIs are tantalisingly mysterious.) The general problem is providing a way for the programmer to (schematically) specify the URIs and handlers without getting bogged down in state machine encodings. If someone's got some good ideas here, I'd love to hear about it (on the web-devel mailing list, perhaps). cheers peter -- http://peteg.org/