I'd like to get some ideas on how caching might be integrated into Turbine and Torque.
At my job I've implemented a pattern where data access goes through managers that return value objects, except on large result sets (they are cached where efficient and sorted using a comparator sorter on scaled down value objects or on ArrayLists of arrays). The managers return simple lists for drop downs and the value objects for detail pages. The caching is done at the manager level. Data comes into our application via remote check processing centers and is parsed by standalone parsers. Credit card and ACH transactions processed in batch more also run in standalone mode. All the processes access the data via the same managers and all communicate invalidations through the cache. Conglomerate data is invalidated by adding the summary data cache name to the list of caches to notify of the changes for items. The local and mid-tier caching system keeps the 12 or so machines in synch. It works nicely. Of course some data access is not cached since it needs to be 100% accurate. . . . (Off the subject but a Visa Gateway server certified by Vital would be a fantastic jakarta project. If you ever needed to handle credit card processing, you could turn to an open source solution! I'm sure I could use it in future jobs. Right now you have to buy something less complicated than JCS that costs at least 20k to send files to the credit card processing network. I'm all for starting the project if anyone is interested. You can build a standalone server that takes basic input, formats a file and sends it to a configured provider. There are some tricky error handling issues, but it would be an extremely useful project, but it may put some people out of business.) Back to the point. I could have the managers use Torque for data access and the managers could still handle the caching, but it might be nice to have torque handle some of this on its own. The complexity of handling group dependencies on items matching certain parameters might be a mess, but for item level stuff it would be nice. Sort of like Javlin (sp?) and an appserver all in one. Where might caching fit into torque? What about JCS as a turbine service? Aaron -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
