I mean caching - of course. [Embarassed] a) the loaded module (xml structure describing the form/report) gets a timestamp/version number on the server side b) the client loads the form (xml or whatever is used now to build up the form locally) and caches it locally for further use until the timestamp/version number on the server changes. c) the client loads the data for the form
given the fact that a majority of user (especially remote users) will only use a very limited subset of all available modules ( i have seen smething like 10-20 modules per user out of 1000 in a mid sized company) the traffic can be reduced significantly. BTW I already got a big performance jump by using a compressed ssh tunnel which I needed any way to pass the firewall where only port 22 is allowed. I have no idea if tiny uses a compression for client-server communication. _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
