Yes; originally I only wanted to drop the @password convention, but
people seemed to want to make other changes at the same time.
It's difficult for it to support parameters now because @password
mucks it up; @ is a reserved character, and it's not clear how to
delimit the password from other arguments.
Cheers,
On 15/10/2008, at 8:21 PM, Henrik Nordstrom wrote:
On ons, 2008-10-15 at 12:04 +1100, Mark Nottingham wrote:
FWIW, my original use case was to allow passing arguments to cachemgr
functions, so we can do things like:
This is completely unrelated to changing the scheme. cache_object://
also theoretically supports parameters just as http://
Regards
Henrik
--
Mark Nottingham [EMAIL PROTECTED]
