[8900] in www-talk@info.cern.ch
Caching encrypted data (Re: Non-persistent Cookie proposal)
daemon@ATHENA.MIT.EDU (Larry Masinter)
Sun Aug 13 13:38:31 1995
To: www-talk@w3.org
In-Reply-To: Koen Holtman's message of Sun, 13 Aug 1995 03:09:36 -0700 <199508131009.MAA09987@wswiop05.win.tue.nl>
From: Larry Masinter <masinter@parc.xerox.com>
Date: Sun, 13 Aug 1995 10:29:16 PDT
Resent-From: www-talk@w3.org
Koen Holtman said:
> I think the biggest (web) bandwidth eaters today, and in the future,
> will be picture, sound, and mpeg sites. What you should really worry
> about is such sites going commercial and starting to send their stuff
> in an encrypted form to paying customers, not about stateful services
> getting more common. Do you want to stop the development of shttp?
If each item had its own key, caches could cache the encrypted data,
and providers could send the data keys privately to each client in a
separate (non-cached) transaction.
This would allow caches to cache information that was otherwise access
controlled, even though the cache knew nothing about authentication.
This is a big step from the current web architecture, though.
