OK. Thanks for the feedback. Jérôme LELEU Founder of CAS in the cloud: www.casinthecloud.com | Twitter: @leleuj Chairman of CAS: www.jasig.org/cas | Creator of pac4j: www.pac4j.org
2014-10-22 15:21 GMT+02:00 Marvin Addison <[email protected]>: > > I looked at the KryoTranscoder and I understand how the buffer is > > incrementally extended to get enough space for serialization. > > I never liked that behavior, but it was the best I could come up with > at the time. > > > However I wonder why the serialization process is implemented this way > > because one can use the standard Kryo ObjectBuffer class where we can > > directly pass the Maximum Buffer size. > > I'm not aware of that component. I have noted that recent versions of > Kryo have some substantial API changes over the version that > MemCacheTicketRegistry uses, so perhaps it wasn't available at the > time. I'm fairly certain there is a better implementation strategy > with the most recent Kryo API. > > Best, > M > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
