Yeah, that makes a lot of sense. If really does take some investment to get this all working, but I think it is well worth it in the end. thanks for your input, craig
On Thu, Jun 18, 2009 at 9:25 AM, Victor Kornov <[email protected]> wrote: > With distibuted caches it can be a means of communication. There is no need > for client to send messages to get latest piece of info, the server is in > charge & can update it in teh cache whenever it thinks is the time, keeping > it always up-to-date. In this case cache transcends it's role & becomes > primary data store at least for some data. > If I understand it correctly, local state is important to avoid locks & > sync calls. We have the most viewed data in local state & handle un-common > case of not having something in there appropriately, with a sync call or 404 > or async/ajax calls to get the data in a bit. > > Those are my thoughts. > > On Thu, Jun 18, 2009 at 4:31 PM, Craig Neuwirt <[email protected]> wrote: > >> So is the local state primarily for caching? >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
