Re: [Ginp-developers] Scalability and PicCollections

[Doug C. <do...@cu...>]

Justin wrote:

> Doug,
>
>     I was looking through the Ginp sourcecode and I saw that a major 
> scalability issue is that the PicCollections are loaded for each 
> session that looks at them and then serialized and loaded on each web 
> request. The best fix here is to use the flyweight pattern:
>
> http://www.dofactory.com/Patterns/PatternFlyweight.aspx
>
> So we have ONE in memory collection of pics that all sessions use and 
> their extrinsicState (The customization for each user) is passed into 
> them from the client request for each operation.  This is probably 
> good to do at the same time as the database integration.   I'll be 
> taking a look at this today.  In the meantime I did a bit of work on 
> the GinpServlet today.
>
> Regards,
>
>     Justin

Sounds good. 

The original idea was to keep small amounts of data in memory (String 
pathSelected, String[] PicturesInCurrentFolder) but I think we will soon 
have a collection of beans that will only get bigger and like you say 
they can be shared and the users model can store only state info.  Go 
for it.

>
>
>
> -------------------------------------------------------
> 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
> _______________________________________________
> Ginp-developers mailing list
> Gin...@li...
> https://lists.sourceforge.net/lists/listinfo/ginp-developers
>


-- 
Doug Culnane
do...@cu...
www.culnane.net