The current SplitFile metadata spec doesn't specify block sizes.

Why was this done?

Clients need to know the block size in order to implement reading 
byte ranges efficiently.  e.g. to support the HTTP Range:  header in fproxy.

I propose that the spec be changed to include a BlockSize field.

-- 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

Reply via email to