Ivo Verbeek wrote:
Did that. Issue 410.
I will close this issue, the problem is that the J2EE spec does not give
you a window into this data. That is why it doesn't work when you
enable J2EE sessions.
What about an extra setting for application scope, like <cfset
this.sessionstorage = "datasource_name"> Where sessionstorage defaults
to "memory" ofcourse. Could be a very powerfull feature. Imagine all
the people making the same decision as I did to migrate to client vars
just because they want session-in- database functionality. Instead,
this could work without much changes in the code, it will remain
"sessions". And all that needs to be done is setting one extra
attribute in application scope. The engine would then have to take
care of dealing with the serialized/deserialized. Ofcourse there will
be limitations. Although I personally don't like it, fact is that you
can put entire components in the session, which will not work for
database. But overall, it could be a very powerfull feature.
This is a feature that has already been implemented and is available
now, if you enable j2EE sessions and let the servlet engine do this for
you. For example, there is a library that lets you page out sessions to
MongoDB within Jetty. It has nothing to do with OpenBD, but OpenBD can
hook into this functionality.
There are other stuff to go to memcache, mysql etc. this is a well
trodden path and is the usual manner for doing distributed/cluster setups.
--
online documentation: http://openbd.org/manual/
google+ hints/tips: https://plus.google.com/115990347459711259462
http://groups.google.com/group/openbd?hl=en
Join us @ http://www.OpenCFsummit.org/ Dallas, Feb 2012
