Gilbert, You can always use a manual caching system. If your application controls all aspects of the site (both user interface and administration) then you programmatically know when the cache needs to be modified.
How you implement really depends on the size of data you're dealing with and the servers you're running. I've known people in the past that will basically cache the entire product database as a query in memory and then use Query-of-Queries (QoQ) to retrieve records straight from the memory cache. You can store the cached query as an application variable and maintain the data pretty easily. You can also manually create a structure in your application scope that stores all product/designer information. Just manage this cached data the same time when writes to the database occur. That way the information in the database and the cache stay in sync. -Dan ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:241221 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
