From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00, PP_MIME_FAKE_ASCII_TEXT autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII X-Google-Thread: 103376,15267b2c375b45c2 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-10-24 06:30:12 PST Path: archiver1.google.com!news2.google.com!fu-berlin.de!peer01.cox.net!cox.net!cyclone1.gnilink.net!spamkiller2.gnilink.net!nwrdny01.gnilink.net.POSTED!53ab2750!not-for-mail From: "Stephane Richard" Newsgroups: comp.lang.ada References: <3F92BEAA.9030004@comcast.net> <3F97EBFD.8040901@comcast.net> <3F9879DA.6070205@comcast.net> Subject: Re: Ada Component Registry proposal X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: Date: Fri, 24 Oct 2003 13:30:10 GMT NNTP-Posting-Host: 129.44.81.217 X-Complaints-To: abuse@verizon.net X-Trace: nwrdny01.gnilink.net 1067002210 129.44.81.217 (Fri, 24 Oct 2003 09:30:10 EDT) NNTP-Posting-Date: Fri, 24 Oct 2003 09:30:10 EDT Xref: archiver1.google.com comp.lang.ada:1598 Date: 2003-10-24T13:30:10+00:00 List-Id: "sk" wrote in message > > I know I should wait for your HTML publication before asking, > but have you allowed for a mechanism, within the Registry, > which will ensure that a potential user does not quickly > get annoyed by dead-[links,entries] and give up using it ? > > -- > ------------------------------------------------- > -- Merge vertically for real address > -- > -- s n p @ t . o > -- k i e k c c m > ------------------------------------------------- > I think I can answer that one well to a certain point :-). You see, ultimately we could do a bot of our own crawling the web as per the list of URLs tha appear in the XML file and write a log (successful or non successful) in trying to get to the library's webpage. The library authors would need to assure to update such things as URL Changes to their libraries or to noticy somehow (via email perhaps) or simply by udpating the XML file that the library is out of commission or could be taken over by someone else. Likewise we could also, instead of linking to, hosting the libraries themselves so that it doesn't become the responsibility of the author but of the library maintenance team to assure proper linkage to available source code. Of course this last suggestion is pending the author's approval to have his library hosted (or mirror) on the library website.(in lieu of or in addition to the current place where the library is hosted). Just for the sake that should the author's current location go down or the library is abandonned (for any reason) then perhaps another programmer can continue it's development right on the website). Of course, as mentionned, this would work provided the library authors agree to having us host the code (or mirror ir) locally here. Having each library element hosted locally would give us full control over the availability of the library which does have it's advantage :-). not to mention an instant backup for the authors in case their other hosting places go down whether for maintenance or permanently we'd still have their library(ies) there for them. -- St�phane Richard "Ada World" Webmaster http://www.adaworld.com