From: Steve V. <vi...@ie...> - 2009-10-20 13:46:26
|
On Tue, Oct 20, 2009 at 7:40 AM, David Hayek <dh...@sw...> wrote: > Hello > > By way of background, my current job involves programming J2EE > applications. But I discovered Erlang and Yaws a while back and have been > working with them in my spare time ever since. > > One of the things I like about the J2EE servlet specification is its > handling of sessions as a way of storing arbitrary data across user requests > in a hash table. I know Yaws has cookie-based sessions, but no formal way > to set and get attributes for a user's session, so I created the session > module below for a project I'm working on now. > Have you considered that encouraging session state goes against the tenets of the REST architectural style? Servlets were designed at a time when REST and its constraints, especially its statelessness constraint, were understood thoroughly by only a handful of people on the planet, but thankfully that knowledge has spread and the rest of us have collectively learned much since then about designing RESTful web applications. I'd be interested in hearing more about why you think you need stateful interactions of the session variety. Have you read this: <http://oreilly.com/catalog/9780596529260> --steve |