One last thing. If you write anything away, the data in the cache will become stale unless it's updated, or the cached data is removed. If you have a client side cache and don't handle this, you could have two different clients having a different view of the data (one a stale cached version, the other an up to date version).
If you have data in a server side cache that is stale, all of the clients will be showing out of date information.. Good luck. Paul ----- Original Message ----- From: "seemaherein" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, September 19, 2007 2:25 PM Subject: [flexcoders] Re: caching in Flex > sure, i'll let you know. > I am a starter with all this. and really thankful to you for your > valuable suggestions > > --- In [email protected], "Paul Andrews" <[EMAIL PROTECTED]> wrote: > > > > Remember to have a way to turn the cache on and off - then you can > measure > > how effective it is. Naturally, it takes time to fill a cache with > enough > > results before it becomes effective. > > > > A server side cache is effectively saving you the time involved in > a > > database query (for all clients), but not saving you any transfer > time for > > the results ( which may be significant for large amounts of data). > I don't > > think that you ever said what "large" was! > > > > A client-side cache would save you db access time and transfer > time, but > > only for that specific client. > > > > Let us know how good the improvement is! > > > > Paul > > ----- Original Message ----- > > From: "seemaherein" <[EMAIL PROTECTED]> > > To: <[email protected]> > > Sent: Tuesday, September 18, 2007 8:11 AM > > Subject: [flexcoders] Re: caching in Flex > > > > > > > Thanks Paul & Tom > > > I'm planning to implement server side cache. > > > > > > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com > Yahoo! Groups Links > > > >
