Web App Pattern Language

a Pattern Language/Best Practices for WebApp development

Gads I wish there were one. Or maybe there is already and I need to look harder.

• Jun'2012: just found the Twelve Factor App model.

Desire: language-neutral discussion of approaches to various issues that come up. Authentication, designing URI-s (ReST), Object-Relational crap, etc.

Object Identifier (likely to drive URI): Joshua Schachter says don't use an auto-increment integer. Consider using the MD5 of some unique property to the object, perhaps. I'm not sure I agree, but perhaps it depends a lot on the context. Certainly you'd want that property to be both unique and unchanging.

Web Authentication

Web Cookie

Web Form Flow - interface, app code style, etc.

Database Abstraction

ReST:

• make a query (with no side-effects) an HttpGet (this makes the screen bookmarkable, among other things)

  • what if you want to "hide" some params? (why?)

• make anything that does have side-effects an HttpPost

  • once it's done, redirect to a URI that's a view/query (back to HttpGet)

  • Post Once Exactly (POE) from Mark Nottingham http://www.ietf.org/internet-drafts/draft-nottingham-http-poe-00.txt

    • do Continuation-s take care of this?