On Fri, 26 Jul 2002 20:31:43 -0400 Gianni Johansson <[EMAIL PROTECTED]> wrote:
> With the current FCP implementation would be application writers have > to handle metadata parsing for redirects themselves. This seems like > an unreasonable burden, especially given that Oskar has already > written a metadata handling system. > > I propose that we add an optional MetadataHint message to the > ClientGet FCP handling. This message, sent after the final DataChunk, > would contain the next URI to request if the request was a redirect. > > While somewhat less ambitious (read easier to implement) than the > initial FCP level 2 proposal, MetadataHints would allow application > writers to easily handle redirected requests without having to parse > metadata. > > I checked in an initial implementation. Look here for a little more > info: > > http://hawk.freenetproject.org/pipermail/cvs/2002-July/000351.html > > What do people think? o/~ I think I love you o/~ Definitely looks pretty well-done, and convenient too. There's no chance of having it somewhere other than last, though? the part of my library that actually handles parsing things has two sections, ->parsemeta(), and ->data(). And it's after a call to parsemeta (but after data), that I figure out whether we're doing a redirect or what. I kinda like the idea of keeping control stuff first and "real" data last. Anyway, whether or not _I_ end up using it, it's definitely a nice thing to have. :)
msg03525/pgp00000.pgp
Description: PGP signature
