Slides - Common Lisp.net

More documents

Recommendations

Info

It’s HTTP’s fault• HTTP, which is an asynchronous andstateless protocol, considers every request/response as an independant object.• Developers consider every request andresponse as a part of a sequence ofinteractions.
What do we want to say?An application is not a set ofdistinct pages as much as aset of sequences of pages.Example: First we show theshopping cart page, then, ifthe user wants, they cancontinue to the payment infopage, finally they can viewthe confirm order page.CartPaymentConfirm
Page 1 and 2: UnCommon Webor: How I Learned to St
Page 3: The Problem• The tools don’t al
Page 7 and 8: Continuations• Continuations are
Page 10 and 11: Example(defaction purchase (cart)(s
Page 12 and 13: Continuations in UCW• Simulated b
Page 14 and 15: Actions• Every user action (follo
Page 16 and 17: Rendering• Every component must,
Page 18 and 19: TALTemplating library which puts co
Page 20 and 21: The RERL Protocol• The handling o
Page 22 and 23: class request-contextall the inform
Page 24 and 25: class session-framea single interac
Page 26 and 27: class applicationset of entry-point

Slides - Common Lisp.net

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?