Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeds.phibee-telecom.net!usenet.ukfsn.org!not-for-mail From: Martin Gregorie Newsgroups: comp.lang.java.programmer Subject: Re: demise of sun.com Date: Tue, 18 Sep 2012 19:41:12 +0000 (UTC) Organization: UK Free Software Network Lines: 25 Message-ID: References: <80d858l76kch632v7gdefamcecl18a646t@4ax.com> <821958dsvuebbng74ded6o3g436al8iktj@4ax.com> NNTP-Posting-Host: 84.45.235.129 Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: localhost.localdomain 1347997272 30744 84.45.235.129 (18 Sep 2012 19:41:12 GMT) X-Complaints-To: usenet@localhost.localdomain NNTP-Posting-Date: Tue, 18 Sep 2012 19:41:12 +0000 (UTC) User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2) Xref: csiph.com comp.lang.java.programmer:18826 On Tue, 18 Sep 2012 04:27:39 -0700, Roedy Green wrote: > There is a similar problem with RFCs. Old ones don't have a link to the > new replacement. > ...but there's a known solution for RFCs - the RFC search engine http://www.rfc-editor.org/rfcsearch.html This takes an RFC number or a word/phrase in the RFC title and digs out the referenced RFC plus a chain linked forward and backward to show all the RFCs your taget obsoleted as well as those that make it obsolete. > The author of a deleted document could most easily set up a forward link > faster than even one user could research it. > Sure, but using the search engine is easier for both author and researchers. ... I now return you to the scheduled program. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |