On Saturday 11 September 2010 09:32 (CEST), Kim Holviala wrote: > This got me thinking about my failed attempt at extending the protocol > to make it possible for the client to include metadata in the request. I > had to scrap the extensions because some servers just didn't like the > extra stuff... So, with caps.txt the client could first query the server > about the protocol, and if caps says it's ok to have extra metadata then > it could send 'em. > > Or something like that. > > Comments? Ideas? IMO, unlike your previous attempts, this one seems the best way to go. :) The only risk is that your extension won't catch up, and only 1% of the gopherspace will use it, while other extensions will come, and we might end up with plenty of extensions, with clients supporting only this or that one... But again - the idea behind CAPS and protocol-detection sounds okay to me. Best regards, Mateusz Viste -- You'll find my public OpenPGP key at http://www.viste-family.net/mateusz/pub_key
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Gopher-Project mailing list Gopher-Project@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/gopher-project