3 ms·
It's an unnecessary detail (the continuation I mean) there is no need to bother the user of the framework with that detail. It's hidden in code like this... (c
by vikram 19y ago
It's an unnecessary detail (the continuation I mean) there is no need to bother the user of the framework with that detail. It's hidden in code like this...
(call 'componentname :param1 value1 :param2 value2)
and
(defaction are-you-sure ((q question) answer)
(if (string= answer "y")
(call 'excellent)
(call 'tobad)))
Question excellent tobad represent pages/widgets. Here question probably has a form which has a field called answer and the submit binds to the action are-you-sure.
Thing to note: The workflow is defined easily and is very clear.
[sorry I couldn't get this to indent]
- mike_organon 19y agoContinuation-style webapps are supposed to make programming easier, but doesn't that contradict REST principles for webapps? I think it would be preferable to have a good framework (for lisp!) that supported REST-style. I would expect the continuations-style holding session state would lead to problems once you get past prototyping. Also, can you make cool urls for bookmarking?
- papersmith 19y agoAFAIK the continuation-passing style is designed to write desktop-like web apps with interactions too complex to model on plain HTTP. But if you have to use static URLs, you can still explicitly specify them.
- vikram 19y agoActually bookmarking is an issue with what I am doing so for now I'm using a redirect to get the url cleaned up. For example if you want to get timetable from London to Brighton then you search and the results are on a url like /timetable/london/brighton. There is a way to change the url but that only half works for me. I still get urls like timetable/?from=london&to=brighton