[10483] in www-talk@info.cern.ch

home help back first fref pref prev next nref lref last post

Re: CGIs to manage backlink information

daemon@ATHENA.MIT.EDU (Benjamin Franz)
Tue Dec 17 14:37:15 1996

Date: Tue, 17 Dec 1996 11:24:54 -0800 (PST)
From: Benjamin Franz <snowhare@netimages.com>
To: www-talk@w3.org
In-Reply-To: <199612171620.AA04944@sol.unizar.es>
Resent-From: www-talk@w3.org

On Tue, 17 Dec 1996, Alejandro Rivero wrote:

> > > After my experience with the script to capture REFERRER information
> > > (WWW pages pointing to pages on my server), I took a bit more
> > > of time to be able both to capture and serve such "backlinks" 
> > > within each html page. It could be a good reason
> > > for browser to implement finally the LINK tag.
> > 
> > Perhaps. But my experience (I've been recording and analyzing REFERRER for
> > about a year and a half now) indicates that even a moderately popular page
> > could be swamped with the number of backlinks - it really should have at
> > least one level of indirection -> pointing to another URL with the list
> > of backlinks. 
> > 
> 
> Well, that is exactly the point. LINK information goes to the HEAD part,
> so HTML text is not swamped anymore. Of course, maintenance is needed
> to avoid obsolete links increasing such HEAD. 

Ah, no you missed what I meant. You could end up loading 40K of <LINK>s in
the head before you loaded 4 or 5K of actual <BODY>. You should have a
link to another URL *which contains* the full list.

-- 
Benjamin Franz


home help back first fref pref prev next nref lref last post