Pre-Grant Publication Number: 20070180110
Collaborate on the process of community review for this application. Posting will not be forwarded to the USPTO. Flagging a post as an ACTION ITEM signals further research. Flagging SPAM and ABUSE helps to manage discussion. Placing double brackets around a reference to a claim or prior art will create a hyperlink to the original ex. [[claim 1]] and [[prior art 2]].

Please review the Community Code of Conduct prior to posting

Discussion (4)
  Facilitator's Comment     Action Item
  Show without Noise
3
Mel Beckman (over 5 years ago)
Regarding Claim 00010 Here is just one example of this kind of session management mechanism, in this cae for the ColdFusion web application development environment, described in detail in the article "Encapsulating Sessio State Management" (http://coldfusion.sys-con.com/read/42075.htm). There are similar examples of such mechanisms built into many other web application programming systems, including PHP, J2EE, and Ruby on Rails, just to name a few.
2
Anthony Phillips (over 5 years ago)
As far as I can see there is no inventive step in this disclosure. Microsoft's premier web technology ASP.NET has had database session state management since 2000. ASP.NET's session state storage is very flexible allowing a runtime decision between in process, out of process or database storage.
Roy Hodges (over 5 years ago)
Agreed, using object mapping in data managers that use ASP.net session state to store values has already been done by many, including myself since ASP.net was first released in beta.
1
Walter Dietrich (almost 6 years ago)
I've only read some of the independent claims, but it seems to me that J2EE servers from IBM and BEA have been doing this kind of thing for a while now. I think BEA is able to store sessions in main memory and share them across servers. I think IBM is able to store sessions in RAM or databases and share them across servers. The only question is how the association between clients and sessions persists when servers go down, but I think the systems handle that by using cookies or URL rewriting. That's probably in the J2EE spec.