> Now, at this point, the client *has* to decrypt the metadata, parse it as > a FNP style message, and find the content-type to find out if its a > special freenet metadata section.
The client has to decrypt the metadata and find the content-type anyway. That's what clients do, they fetch the file, decrypt it, find the content-type, and then deal with the file appropriately based on what type of file it is. If the metadata is in an unreadable format, it won't be able to determine the content type and so won't be able to do anything with the file except for display the undecipherable metadata to the user and save the data to disk. So if the file is a redirect formatted in XML then the redirect won't work. But in your system it won't work either. You just specify that redirects, etc. have to be FNP. I will also specify that if you have a special file, then it must be formatted in FNP in order for FNP clients to read it. But it can also be formated in XML in order for XML clients to read it. > Either way is a tremendous waste of time, since > > ( Metadata-length - Data-length == 0 ) > > takes a nanosecond on a processor. I think a better solution would be explicitly state what kind of metadata was in the metadadata field. Metadata-format==0 (0 for FNP, 1 for XML, etc..) is faster. I'd prefer something more explicit such as Metadata-format=="FNP" which shouldn't take much more time and would be much more explicit. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
