IDP Cluster going forward (JDK 7)

Cantor, Scott cantor.2 at osu.edu
Fri May 31 18:47:16 EDT 2013


On 5/31/13 6:25 PM, "Manuel Haim" <haim at hrz.uni-marburg.de> wrote:
>
>This problem exists at least with the Kerberos login handler or the
>x509 login handler: After serialization and de-serialization, the
>transient information has gone and will not be recovered, thus the
>shared object is worthless.

I'm not sure if transient is the right term here, I think this is just
non-serializable data. Transient fields are explicitly supposed to not
need saving.

But yes, this is exactly why he picked Terracotta to begin with. Using
object serialization has never been part of our plans.

>Our Memcache plugin makes use of the Apache BeanUtils. Whenever a
>local object is synchronized with an global object from Memcache (and
>the global object is newer), I need to beancopy its values to the
>local object (in order to retain the current object reference which is
>already held by some other method of the current IdP instance). Of
>course, a dumb StorageService (e.g. keeping only Strings and being
>queried on every data change or retrieval) would solve that problem,
>but that's not the way how the current IdP 2.x utilizes the
>StorageService. (Instead, the whole Session object is usually
>retrieved only once on each HTTP request, and then heavily altered
>every now and then, without ever being put back.)

Thank you, that fills in a missing piece for me.

Needless to say, "a dumb StorageService" is exactly my requirement for V3.
That doesn't solve the problem of serializing data, but that's something
people will just have to supply if they want to preserve custom objects.

We are still discussing what to do right now, but I'm encouraging people
to take a look at what exists (and hopefully Paul's database plugin if we
can get it) so we can decide what the best interim plan is.

In the meantime, we are not asking people to stay on JDK 6, and we will
try to be as flexible as we can in helping resolve any problems people
have with third party options within the constraints of our resources.

-- Scott




More information about the users mailing list