Re: [Wicket-develop] should we make AbstractResource serializeabl e or not?

Tue, 08 Mar 2005 08:02:58 -0800

Title: RE: [Wicket-develop] should we make AbstractResource serializeable or not?
yes that is why i asked it here :)

But then we really have to check everything that holds those Resource Instance.
Because maybe the AbstractResouce should be serializeable but a implementation of that is responseable what it serializes..

johan


Christopher Turner wrote:

I think making resources serializable is a BIG risk in that images or similar can be quite large and you could end up with a lot of them if they are on a page that is used regularly, thus you run a big risk of degrading application server performance very quickly. I would suggest that all resources are non-serializable but with enough information maintained in the session to be able to recreate them at a later date (detached resources anyone?).

Regards,
Chris

>
>
> Our clone by serialize did encounter a few serialization
> exceptions for
> example
> all the Resources (like image). Should we make AbstractResource
> serializeable?
> those can be in the session..
>
> johan
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from
> real users. Discover which products truly live up to the
> hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396> &op=click
>
> _______________________________________________
>
> Wicket-develop mailing list [email protected]
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
>
>

Reply via email to