[
https://issues.apache.org/jira/browse/WICKET-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046019#comment-13046019
]
Martin Grigorov commented on WICKET-3778:
-----------------------------------------
Good point. It is not only for pages.
IObjectSerializer ?
What do you mean about IObjectStreamFactory?
It is used only by WicketObjects which is the delegate for JavaSerializer from
my patch. JavaSerializer will be the default serializer so I cannot remove them.
IObjectStreamFactory can be replaced with :
WicketObjects.setObjectStreamFactory(new GaeObjectStreamFactory());
> Add possibility to register different page serializer
> -----------------------------------------------------
>
> Key: WICKET-3778
> URL: https://issues.apache.org/jira/browse/WICKET-3778
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-core
> Affects Versions: 1.5-RC4
> Reporter: Martin Grigorov
> Attachments: wicket-3778.patch
>
>
> Currently Wicket uses default Java serialization to persist/load the page
> to/from the backing stores.
> There are serialization libraries which claim to be more performant than Java
> serialization.
> With this ticket I want to make Wicket more configurable by introducing
> IPageSerializer interface with Java serialization as default implementation
> (as it works today).
> Additionally I'll add an implementation based on
> http://code.google.com/p/kryo/ in wicketstuff project at Github.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
