kampers.net

Idea: SOAP is really cool, but what if you’re dealing with a web service that could possibly be unavailable? And your application is loading data at runtime? It would be great if there were a framework for caching retrieved data. In fact, you could have a system where you register pieces of information you want to have updated by your “SOAP cache” framework, and it would get them for you every X minutes. Then you load them locally from the cache—fast! If the web service goes down, you still have a relatively recent copy of the data.

This would be kind of useless for apps like remote authentication, but would be killer for data-based apps like fetching prices from Amazon or charts from a music database. #