Three, two, one...Geronimo!, Part 3: Issues of state (developerWorks) [LWN.net]

IBM developerWorks looks at Apache Geronimo. "Though computers and the Web make daily tasks more convenient, they also give rise to new challenges. Today's Internet no longer functions simply by responding to requests for HTML-coded Web pages. Nowadays, Web sites must maintain mountains of information about users and be able to manage many complicated tasks. Luckily, leading-edge tools can simplify such issues of state. Discover an industrial-grade solution to this age-old problem -- namely, session state. This article demonstrates how Apache Geronimo maintains the state of thousands of simultaneous connections so that IT managers can breathe easier."

to post comments

Three, two, one...Geronimo!, Part 3: Issues of state (developerWorks)

Posted Nov 21, 2006 12:36 UTC (Tue) by DG (subscriber, #16978) [Link] (1 responses)

The article seems to dress up the relatively easy task of handling HTTP Session state on a server (when using J2EE)

"Nothing to see here, move along."

Agree, nothing Geronimo specific here...

Posted Nov 22, 2006 9:40 UTC (Wed) by fredrik (subscriber, #232) [Link]

This information wasn't Geronimo specific, but general to any J2EE servlet container. There must be millions of pages with a Hello World of web application session management out there already.

If people want to help spread the use of Geronimo, there is literally tons of writing needed on how to understand and configure MDB:s, message queues, persistent storage, talking on proven patterns for writing resource efficient services in J2EE, etc...

Fredrik Jonson