Object Caching [Was: JDBC Class Abstraction]

According my observation the Swing views ask their model very often (e.g. even when moving the mouse over a JTable). Therefore my question: In this case is it recommended to do an additional client side caching of the data? In order to keep the views of all clients consistent, there is an additional synchronisation of all object copies necessary. Does someone know a description (WhitePaper) of such an architecture in the Web?

Thanks,
Bernhard Fischer

Joseph Weinstein schrieb in Nachricht <382858E0.C6753FE3_at_weblogic.com>... [...]
> For now, I'd suggest a middle tier that concentrates client requests,
and
>caches relevant data asynchronously so every client request needn't involve
>the DBMS. If desired, the middle tier can notify clients if specific data
has
>changed since they got their last copy. Clients should communicate with the
>middle tier using light-weight fast protocols like RMI and or JMS.
>
>Joe Weinstein at BEA, the home of WebLogic
>
>Sameer Utrankar wrote:
>

[...] Received on Thu Nov 11 1999 - 02:24:34 CST