Re-opening this vociferous debate now is ridiculous. While never liked the current scheme, it is implemented, tested and debugged. And I have to admit that using a unix epoch date simplifies writing clients.
The real issue is not the format, it's that people want easy access to content indexed by DBR's for times other than the current instant. Here's how to make the complaints go away: 1) Add a page a form page to fproxy that converts from hex suffix values to human readable date values. This will remove the element of mystery for non-programmers who don't understand what is going on. 2) Modify Freenet.client.AutoRequester to support using an effective time property so that you easily get DBR redirected content for dates besides the current instant. 3) Modify fproxy to accept time URL prefixes. e.g. /PAST_1/coolsite// -- The previous update /FUTURE_1//coolsite// -- The next update /DBRDATE_200111281800//coolsite// -- The update for 6PM, Nov 28, 2001 GMT Use the setEffectiveTime() property in 2) to have fproxy retrieve them. I am kind of perplexed and baffled that that this debate should be re-opened again after all the time that was already wasted on it. Why not use this energy to figure out why the network isn't working? -- gj -- Freesites (0.3) freenet:MSK at SSK@enI8YFo3gj8UVh-Au0HpKMftf6QQAgE/homepage// (0.4) freenet:SSK at npfV5XQijFkF6sXZvuO0o~kG4wEPAgM/homepage// _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
