Re: URLs, fopen wrappers and RFC 2718

Hi Derick, I like it too, but (and I hate this "but") its not an rfc2396 compliant scheme name. Valid characters in the scheme part are: alpha digit "+" "-" "." So how are these? crypt-des://blaat.txt crypt-blowfish://blaat.txt compress.zlib://file.gz compress.bzip2://file.bz2 crypt+des://blaat.txt crypt+blowfish://blaat.txt I think I prefer your parentheses, but a second best would be using "-" (IMHO). I think it is important that our wrapper urls can be parsed using parse_url() without changing it's behaviour. Hmmm. I really like the parentheses, it's just not standards compliant :-/ --Wez. On 18/04/02, derick@php.net wrote: > how funny, I was discussing this issue with Stig on IRC too. I want to > implement encryption with streams too for the new encryption extension, > and we came up with something like this: > > crypt(des)://blaat.txt > crypt(blowfish)://blaat.txt > > and then something for zippers: > compress(zlib):// > compress(bzip):// > > seems another viable idea to me...