On Sun, Jun 03, 2001 at 03:03:08PM -0700, Ian Clarke wrote: > On Mon, Jun 04, 2001 at 12:04:23AM +0200, Oskar Sandberg wrote: > > > So a URI is actually a URL, and it just lets you find URLs? Not sure > > > that there would be much point... > > > > IIRC URI is just a more general term for the same thing as URL. > > I know, but in this sense, you are suggesting (if I am right) that the > search returns a URL - ie. a location of some information on a > particular host.
I'm suggesting that it returns a definite address to the data, which could be a URL like http://www.curvecomm.com/teletubbies/po.gif https://safetubbies.net/po.jpg ftp://teletubbypfiles.org/po_large.tiff or a URI on an information network like: freenet:SSK at uagh9paorhngbiauir7484ba/teletubbies/po.png http://freenethost:8081/SSK at uagh9paorhngbiauir7484ba/teletubbies/po.png oceanstore:a4b974ahp98hap98thap98tyap9tyap948tha948 leetnet:GIMME{po-and-the-bong.mpeg <--- far 0ut!!111!!!} Obviously which link you would follow would have to be dependent on your preferred level of security and which networks you can access, just like it would depend on which of the fileformats you can view. If the the output from the search uses a well defined structure, the agent could sort through it and exclude files you can't access or view for you. What I'm saying is, that if you want to make a search service, there is no reason to bind it to data that can be retrieved via Freenet, so in that sense it is a very separate problem. -- 'DeCSS would be fine. Where is it?' 'Here,' Montag touched his head. 'Ah,' Granger smiled and nodded. Oskar Sandberg oskar at freenetproject.org _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
