From owner-freebsd-chat Tue May 11 14: 4:25 1999 Delivered-To: freebsd-chat@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id CE47A15C6F for ; Tue, 11 May 1999 14:04:17 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Tue, 11 May 1999 14:04:15 -0700 From: "David Schwartz" To: "Terry Lambert" Cc: Subject: RE: Europe says yes to spam Date: Tue, 11 May 1999 14:04:14 -0700 Message-ID: <000101be9bf1$d35c7cb0$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <199905112050.NAA19560@usr04.primenet.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > FWIW, I believe something like this will be necessary, as more and > more companies "improve" their sites with "dynamic content", and > simultaneously suck the agregate banwidth down into the toilet. The basic idea is that it should be possible to work up a logical caching scheme were everybody wins. The operators of the caches benefit because they save bandwidth. The web page providers benefit because they save bandwidth. If caching is implemented properly, nobody loses. Hit counts can still be measured based upon the dynamic portions with as few actual bytes changing hands as possible. Unfortunately, at present, the only tool available to allow parts of a page to be cached and not others is frames (or custom java/javascript). And frames are ugly and awkward. If your only goal is to switch out a graphic on page views, the actual amount of dynamic content is small. The problem is that the graphic is in the middle of a page, and the rest of the page's contents are larger. I think a good solution would be something to allow browers to piece together pieces of pages using something similar to shtml. That way the browser could make a single connection to a caching proxy, get the static portion of the page, and then go on to request the rest of the page through the same connection with the cache acting as a 'pass through'. Perhaps something like :
Static alternative
It might take some work to make something like this look reasonable while the page is loading though. That way the majority of the data could be made static and only the truly dynamic portions would have to be refetched. David Schwartz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message