Jeff, I understand the concepts about distributed updates.
But what, if the URLs are individuel? Say you get a session ID for your individual update and all your parts have it, too? So for the cache, the URL looks different and the content is different, too. For user 1111111 you get the urls: A is www.update.com/updates/pack_A_1111111.asp B is www.update.com/updates/pack_B_1111111.asp C is www.update.com/updates/pack_C_1111111.asp And user ZZZZZZZ will get A is www.update.com/updates/pack_A_ZZZZZZZ.asp B is www.update.com/updates/pack_B_ZZZZZZZ.asp C is www.update.com/updates/pack_C_ZZZZZZZ.asp And of course, they won't use User-Ids but 'session' ids. This is only *one* very simple idea that could prevent caching (and could be implemented to collect statistical data about the updates customers request). So did any1 actually test it, that caching will work? -- Holger Lembke +49-531-334676 ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/
