At 07:41 PM 08/31/2002 +0100, Matthew Toseland wrote: <big snippage>
>So an alternate date format may make sense... how about > >/DATE at YYYYMMDD/SSK at ...? SSK at blah/blah at YYYYMMDD ? @ is reserved in >keys, >isn't it? > >I want old-edition links to work without invoking click-through security, >because >they represent no conceivable security risk above regular links. The other >possibility is to special case ?date=YYYYMMDD<end of URL> in the parser. > >Any suggestions? I started looking into a similar idea and I stumbled on this so-called metainfo field of a FreenetURI string. It apparently isn't used anywhere yet, since I couldn't find a call to FreenetURI.getMetaInfo(). This metainfo apparently can be optionally included after the crypto key in a FreenetURI string as a series of name=value pairs. I don't know if it can be included when there is no crypto key specified in the FreenetURI string (like in typical SSK strings). Would we better off handling this date-specification stuff in FreenetURI and then when the corresponding request object is created, construct the MetadataSettings from the metaInfo that was contained in the original FreenetURI string? This would enable this feature to work everywhere instead of just in Fproxy. Maybe this doesn't make total sense, but I thought I'd throw it out there and see what people think, especially Matthew Toseland (and others?) who is actually working on code to get this feature finished. Thanks! Ed _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
