The metadata contained in
SSK@FKIV74~piybEZHYVnCw0rg7qnfMPAgM/HourNodeStatus is pasted in
below. This is the only DBR I know of that has both a non-default
offset and increment setting. It has an hour increment and a 10
minute offset. Note that the numbers are in hex as I believe all
numbers are in the used-all-over-Freenet FieldSet's.

I think the rule is to insert the dbr-calculated time after the
first slash in the target URI, but I am not sure. I do know a good
example would be
SSK@SSK@rBjVda8pC-Kq04jUurIAb8IzAGcPAgM/3d891380-TFE where the
3d891380 represents the offset to the appropriate time since the
epoch in hex (it is calculated in the date redirect metadata
handling code of the client). The second that started 2002-09-19 UTC
was second number 3d891380 in hex. Since freesites like TFE have no
Increment nor Offset in their DateRedirect settings, they default to
a 0 second offset and a 24 hour increment. So, until it falls off of
Freenet, you can view the 2002-09-19 edition of TFE with the
FreenetURI SSK@SSK@rBjVda8pC-Kq04jUurIAb8IzAGcPAgM/3d891380-TFE

This is the metadata for
SSK@FKIV74~piybEZHYVnCw0rg7qnfMPAgM/HourNodeStatus

Version
Revision=1
EndPart
Document
DateRedirect.Target=SSK@FKIV74~piybEZHYVnCw0rg7qnfMPAgM/NodeStatus
DateRedirect.Increment=e10
DateRedirect.Offset=258
End

Ed

At 07:55 PM 09/18/2002 -0700, Tyler Riddle wrote:
>I was not able to find the spec for how the metadata
>for a DBR looks. I am especialy interested in the
>metadata for a DBR with a non-standard redirect time.
>What does that look like?
>
>Also how is the freenet key translated to deal with
>the DBR? If the metadata is
>
>Version
>Revision=1
>EndPart
>Document
>DateRedirect.Target=freenet:SSK@rBjVda8pC-Kq04jUurIAb8IzAGcPAgM/TFE
>End
>
>What is the client going to wind up requesting? Is it
>something like SSK@foo/TFE/<seconds> ?
>
>Thanks,
>Tyler
>
>=====
>AIM:rllybites    Y! Messenger:triddle_1999


_______________________________________________
support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support

Reply via email to