Although cache can be implemented externaly (and must be) but, how many times you can see the same java, css or image beeing transmited between client and server?.
Once you try to implement SSL as a need in the comunications, I suggest to add a "firm" in the server objects. When the client ask for an element the first time he will send an empty firm to the object. Then, the server will send the firmed object down. The second time, the client will ask the object with the firm it own. The server will check the firm received with the firm of the object hosted, if the firms are equals, the server will send an up to date signal to the client, and no object transmision will be done. Yes, it seen to be trivial, but I can see it every day at my job while monitoring http trafic. Always the same, the proxy server doesn't work, the expire date is short, etc... And what it´s more, I experienced a high latency, ending with an application hang, with an applications that used a client cookie to store data, not only session data. The same cookie (realy no changes where made) were transferred from one form to another. The server must support this feature too, but it can be easily identified in the client. Kind regards. -- Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss
