As in regular C1DataObjects, Express edition components in WebDataObjects for ASP.NET can be used in cases where you don't need independent and reusable business logic and ease of use is more important to you than functional richness. Express components reside directly on your Web forms (Web pages) and cannot be reused across Web pages.
Working with Express edition, you use C1WebExpressTable derived from C1ExpressTable, and C1WebExpressConnection derived from C1ExpressConnection. Put a C1WebExpressConnection and one or more C1WebExpressTable components on your Web form and connect the C1WebExpressTable components to the C1WebExpressConnection. Unlike C1ExpressTable, C1WebExpressTable must always be connected to a C1WebExpressConnection.
You can also use the C1ExpressView component that belongs to the regular C1DataExpress. C1ExpressView does not have Web-specific functionality, so there was no need to create a special counterpart for it in C1WebDataObjects, the regular C1ExpressView is enough.
C1WebExpressConnection has special object properties called CacheProperties and SessionCacheProperties containing settings for tuning caching behavior. These are the settings on data set level. You can tune CacheProperties if you use global cache and SessionCacheProperties if you use session cache. There is also a Boolean property on table level, MemoryResident that allows you to make individual read-only tables pre-fetched and resident in memory.
To make caching work properly, you need to include some code, certain method calls, usually very simple, in your Web page. These methods are static members of two classes, GlobalCache and SessionCache. These two classes have no instantiated objects, they are just collections of static methods (functions) that you use to control the cache.
|
