Re: cvs: pecl /zip zip_stream.c /zip/examples fopen.php
| From: | Marcus Boerger | Date: | Mon, 13 Mar 2006 20:47:09 +0000 |
| Subject: | Re: cvs: pecl /zip zip_stream.c /zip/examples fopen.php | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-3608@lists.php.net to get a copy of this message | ||
Hello Pierre,
Monday, March 13, 2006, 9:27:51 PM, you wrote:
> On 3/13/06, Marcus Boerger <helly@php.net> wrote:
>> Hello Pierre,
>>
>> Monday, March 13, 2006, 9:07:53 PM, you wrote:
>>
>> > On Mon, 13 Mar 2006 19:52:13 +0100
>> > Marcus Boerger <helly@php.net> wrote:
>>
>> >> Hello Rob,
>> >>
>> >> Monday, March 13, 2006, 2:47:27 PM, you wrote:
>> >>
>> >> > Marcus Boerger wrote:
>> >> >> Hello Rob,
>> >> >>
>> >> >> we were having an interesting discussion with Pierre about that
>> >> >> url layout and he claimed it was your idea to use the '#' as a
>> >> >> separator between archive and entry. Now Pierre is wrong in saying
>> >> >> that # denotes a fragment but the use is quite different from what
>> >> >> he is using it for.
>> >> >>
>> >> >> In terms of the RFC the extensions stream handler is the server and
>> >> >> the php script is the client. Now read what the RFC says about
>> >> >> fragment:
>> >> > Sorry got tied up yesterday.
>> >>
>> >> > While I still think "# "is better than "?" (have seen
>> >> > "#" used for
>> >> > this and reading RFC 3986 it seems to the way to go, I have never
>> >> > seen "?" used), what if it is changed to use "!" ?
>> >> > I did a bit more research on this and this syntax is based upon the
>> >> > Common VFS from jakarta
>> >> > (http://jakarta.apache.org/commons/vfs/filesystems.html) and used
>> >> > in a few other projects.
>> >> > i.e. |zip:// /arch-file-uri/[! /absolute-path/]
>> >> > zip://zipfile.zip!/file.txt
>> >>
>> >> > |A similar approach is also used by Eclipse.
>> >>
>> >> If actually a few other projects are using it i'd appreciate it,
>> >> since imo the worst thing to do is ignoring what others do and
>> >> inventing different stuff for different extensions here.
>>
>> > The ! is a hack as it is the only chat not clearly explained in the
>> > RFC. Was it not the argument to follow the RFC?
>>
>> > One sure thing, ? is out. And about other extensions, I am the first
>> > one to actually propose that (as URI and working), so yes discussions
>> > are welcome :-)
>>
>> Why is ? out becuase i would accept ! or for what reason?
> It is not compliant, definitivally not. It is not used to define a
> secondary resource, the # is used for that, as explained in the
> section 3.5 of the RFC.
I only see one resource and that is the archive and the file in the archive
is obvious an entry/entity of that archive. Thus ? is correct. A secondary
resource would be if you would try to access a ftp stream through a http
locator or alike.
Best regards,
Marcus