Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use of java for serialization does not directly replace ehcache #21

Open
nsiemens opened this issue Apr 23, 2013 · 6 comments
Open

Use of java for serialization does not directly replace ehcache #21

nsiemens opened this issue Apr 23, 2013 · 6 comments

Comments

@nsiemens
Copy link
Contributor

You are using Java to do the object serialization. This turns into a gotcha because the default play2 cache doesn't, and therefore is able to serialize classes that don't implement Serializable. Which causes fireworks when your plugin replaces the default and everything that caches a non-implementer of Serializable breaks because of the additional requirement that your plugin is placing on input to the Cache.

@mumoshu
Copy link
Contributor

mumoshu commented Apr 24, 2013

@nsiemens

Thanks for the info!
I think I have missed about that until now.
Would you mind providing me where I can see Ehcache's object serialization algorithm?

@mwy001
Copy link

mwy001 commented Jul 25, 2013

This is an issue if you want to cache the play.mvc.Result instances. The default Ehcache can do so while play2-memcached cannot.

@mumoshu
Copy link
Contributor

mumoshu commented Jul 25, 2013

Thanks for your feedback, @nsiemens @mwy001 !

I'll write specs for play.mvc.Result chaching and tackle it with twitter's chill.
Further feedbacks and pull requests are always welcome!

@mumoshu
Copy link
Contributor

mumoshu commented Oct 28, 2013

Scala Pickling looks promising but for now it doen't allow serializing/deserializing Any or AnyRefs.

@mkubala
Copy link

mkubala commented Oct 28, 2013

@mumoshu maybe instead of looking for silver bullet which will cover all cases, it will be better to give some basic serializer and allow users to plug-in they own serializers, like the akka's serialization do?

This way we will give control (and responsibility) over performance, backward compability, fields ommiting etc. to the end user.

@mkurz
Copy link
Member

mkurz commented Jul 19, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants