The OCSP (certificate revocation check) doesn't have to be done on every SSL setup - the results can be cached for a while. What is most strange about this art

The OCSP (certificate revocation check) doesn't have to be done on every SSL setup - the results can be cached for a while. What is most strange about this article is the assumption that the backend connectivity is coupled to UI interactivity. That is the single worst thing you can do in a mobile app. They should be decoupled as much as possible. In general the user shouldn't even be able to figure out or care that there is latency in the underlying networking. Of course the one time is when they search for something, but local caching and prediction plus heuristics should help a lot of the time for that. (Of the billions of items on the server, the user is only going to access a tiny subset.) For the developer types this is a nice presentation (with a nervous presenter?) showing best practises for writing a REST Android app. Pretty much all of the principles apply to iOS and other mobile platforms too where you decouple the user interface from the underlying networking. Google I/O 2010 - Android REST client applications http://www.youtube.com/watch?v=xHXn3Kg2IQE http://www.youtube.com/watch?v=xHXn3Kg2IQE