I think that would be something that should be implemented at wicket
core... anybody done this before?

Is there any way to tell wicket NOT to serialize a page? For example
give a timer.... if user does not invoke the page for 1 minutes it
will not be serializeed..?

**
Martin

2012/2/23 Juha Syrjälä <juha.syrj...@gmail.com>:
> Hi,
>
> I would guess that Wicket uses a normal Java built-in serializer by default.
>
> Here are some benchmarks for different serializer implementations
> https://github.com/eishay/jvm-serializers/wiki/ . Java's built-in serializer
> is not the fastest...
>
> --
> Juha Syrjälä
>
>
> On 02/23/2012 08:45 AM, Martin Makundi wrote:
>>
>> But is serializing wicket native components only.. I would assume
>> wicket does it best.
>>
>> 2012/2/23 Juha Syrjälä<juha.syrj...@gmail.com>:
>>>
>>> Hi,
>>>
>>> Wicket 1.5 has support for pluggable serializers via ISerializer
>>> interface,
>>> you could try to plug in different serializer implementations, for
>>> example
>>> this one https://github.com/wicketstuff/core/wiki/Kryo-Serializer . That
>>> should make the serialization bit faster.
>>>
>>> --
>>> Juha Syrjälä
>>>
>>>
>>> On 02/23/2012 05:12 AM, Martin Makundi wrote:
>>>>
>>>>
>>>> Hi!
>>>>
>>>> Any experiences how to optimize the performance of a Page that
>>>> contains nested ListView:s with a total page serialized size of over
>>>> 10 MB?
>>>>
>>>> I have made all actual data objects non-serializable and available via
>>>> loadabledetachablemodel, but page Serialization seems to kill the
>>>> performance in ajax requests where I might be modifying just a single
>>>> cell in the maze.
>>>>
>>>> I tried callinc removeAll at onDetach... it improved performance but
>>>> ofcourse event listeners don't work anymore ;) I could write custom
>>>> event listeners as workaround, though, which would know to call
>>>> onPopulate() before triggering an event.
>>>>
>>>> Any experiences of similar situation?
>>>>
>>>> **
>>>> Martin
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to