[prev in list] [next in list] [prev in thread] [next in thread] 

List:       myfaces-user
Subject:    Re: Pluggable serialization
From:       Thomas Andraschko <zoigln () googlemail ! com>
Date:       2012-01-27 8:03:17
Message-ID: CAMg-+Pqbm=2XozHYFw-HH5C+zc7Rw-_kazHU8ktRbyMysiDQMg () mail ! gmail ! com
[Download RAW message or body]


Hi,

ok :) Can i create an issue then?

Best regards,
Thomas

2012/1/27 Leonardo Uribe <lu4242@gmail.com>

> Hi
>
> I think it is possible to add an SPI interface for serialization. It has
> sense, because that will make easier to the server to hook its own
> serialization provider. Usually it is the container, not the application
> itself who defines which serialization provider should use.
>
> regards,
>
> Leonardo Uribe
>
> 2012/1/26 Thomas Andraschko <zoigln@googlemail.com>
>
> > Hi,
> >
> > i know, there already is an wiki entry which explains how to use JBoss
> > Serialization.
> > I tried this in our application but unfortunately there is mem leak which
> > occurs after some jetty or tomcat restarts.
> > We don't use client side state saving but AFAIK it will also be used for
> > "SERIALIZE_STATE_IN_SESSION".
> >
> > My question is, would it be possible to make the serialization more
> > pluggable?
> > I know for example msm (memcached-session-manager) is using a pluggable
> > serialization for serializing the session to the memcached nodes.
> > It allows to use for example: default java, kyro, xstream or javolution.
> >
> > Thanks.
> >
> > Best regards,
> > Thomas
> >
>


[prev in list] [next in list] [prev in thread] [next in thread]