On Thursday 14 February 2008 14:45, juergen urner wrote: > Matthew Toseland schrieb: > > On Wednesday 13 February 2008 21:44, Jerome Flesch wrote: > > > >> I commited a patch into the node to make it possible to ask for expected > >> > > data > > > >> types with FCP. > >> See http://wiki.freenetproject.org/FCP2p0GetConfig , > >> http://wiki.freenetproject.org/FCP2p0ConfigData . > >> > >> I hope it will help you (anyway it will help me :) > >> > >> For periods, I can't make the data type more specific than "string" at the > >> moment, sorrry. > >> > >> Currently, I'm wondering if it would also be a good idea to convert all the > >> values into basic units (-> in bytes) and let the client apps displays it in > >> a more user-friendly way ? (I'm not really sure how the client would handle > >> values like '1025' ...) > >> > > > > Exactly, there's a reason why we keep the original string. If the user wants > > 12 GiB then we should remember that it's 12GiB and not 12884901888 bytes. > > > > You are right. I change my question to: why are there kbytes and* kibiytes? > I wouldn't mind forcing one or the other upon every other client around by > the way my client handles it.
Because there was no real reason to force one or the other? Feel free to convert it into bytes and offer a slider in your app. > > Juergen -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20080214/cb7a44e7/attachment.pgp>
