What would do you consider to be the best way to handle large amounts of data on the client side? How about from a security standpoint?
I've been looking into the different methods to store and manipulate query results on the client side. The application I've been working on is an intranet site that has rate calculation functions as one of the features.
So far it's been running nicely on the lan but now we are looking to making this available online to provide access to other sites and telecommuting.
As is every single postback results in multiple calls to the database. This is costly in itself and adding more users will just exasperate the problem. The data on the client would need to be encrypted or at the very least obfuscated, and removed at the end of each user session.
What do you consider to be the best approach to this problem?