Great article, Serge! I would offer this viewpoint on the Session concept. The transparent instant availability of an general-purpose Session, as in JSP/Servlet, is ridiculously convenient for about a billion reasons, and therefore a powerful seduction to not really engineer the concept of state and how it applies to your application. This can cause excessive session proliferation and sometimes user frustration, when some operation that should not be expiring in nature suddenly fails because your session expired (for example, my Zimbra mail client, which I otherwise love, does this to me occasionally). And because the typical JSP/Servlet session is a cookie-per-browser Session, and not tied to an individual browser window, Session reliance can cause ugliness when users have multiple windows open to your app. Not everybody remembers that *all* the time. (I'm so guilty as charged).
I'm not implying that session abuse is true in your case :-) Nor that it is reasonable or even possible to implement a meaningful application totally free of the session concept. But we have found at our shop that a lot can be gained by having to think about state, instead of always having "stuff it in the Session" as a omnipresent crutch. I kind of like that Restlet raises this barrier, though I agree with your hypothesis that somebody will inevitably offer it as an, er, option. - Rob ----- Original Message ----- From: "serge" <[EMAIL PROTECTED]> To: [email protected] Sent: Tuesday, September 4, 2007 10:43:51 AM (GMT-0500) America/New_York Subject: some benchmarking is here http://www.naviquan.com/blog/restlet-framework It's rather primitive, but parhaps it can be interesting for the community since it's "before" and "after" moving a site to Restlets, and still not much available on this. Serge
