Wez-
Wow! Thanks for the voluminous descriptions!
I'll print this out and read it in more detail on the train ride home
tonight.
-Pollita
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Hi Sara,
Thanks for making a start on this.
Just a couple of things to note about streams:
A "stream" is an object that exhibits "streamable" behaviour.
A "wrapper" is additional logic that knows about specific protocols (and
encodings) and returns an appropriate stream to access it.
A wrapper ma
It's really a big and nice work.
Thank you Pollita and Happy new year since I've not seen you on IRC.
--
Regards.
M.CHAILLAN Nicolas
[EMAIL PROTECTED]
www.WorldAKT.com Hébergement de sites internets.
"Sara Golemon" <[EMAIL PROTECTED]> a écrit dans le message de news:
[EMAIL PROTECTED]
> Okay,
>
Okay,
An initial draft of the streams reference is in CVS documenting all 14
stream_* functions and providing three examples on the reference page.
While we all wait ((*snore*)) for php.net/manual/en to build, I've got a
local build available on my devbox:
http://169.229.139.97/phpdoc/html/curr
On Fri, 3 Jan 2003, Wez Furlong wrote:
> http://www.php.net/manual/en/function.fopen.php
>
> "Note: The list of supported protocols can be found in Appendix I. "
>
> Appendix I is a link...
OOPS, I was looking through streams API docs
and not wrappers.xml :) This is fine and
not part of strea
http://www.php.net/manual/en/function.fopen.php
"Note: The list of supported protocols can be found in Appendix I. "
Appendix I is a link...
--Wez.
On Fri, 3 Jan 2003, Philip Olson wrote:
> On Fri, 3 Jan 2003, Wez Furlong wrote:
> > Do you volunteer to maintain 2 * (number of translations) of
> Do you volunteer to maintain 2 * (number of translations) of the
> information about which streams/wrappers are present?
>
> That is the reason that I moved the wrapper information into an
> appendix, because it made reading about this stuff difficult (and the
> fopen() reference page unreadable
On Fri, 3 Jan 2003, Wez Furlong wrote:
> Do you volunteer to maintain 2 * (number of translations) of the
> information about which streams/wrappers are present?
Users are not expected to read the entire documentation
of PHP streams API just to get some information on how
to use the PHP fun
Do you volunteer to maintain 2 * (number of translations) of the
information about which streams/wrappers are present?
That is the reason that I moved the wrapper information into an
appendix, because it made reading about this stuff difficult (and the
fopen() reference page unreadable).
--Wez.
> > When are certain streams not available, like, I assume
> > allow_url_fopen dictates the availability of the http stream?
> > FTP module for ftp, etc.
> >
> This is all documented in Apendix I (which is linked a couple times from
> ref.stream), do you think we need to go into it in detail on ref
>--Cross-Post from php-doc discussion thread--
>
> You may want to mention what the following means, this is
> from a phpinfo() on www.php.net:
>
> Registered PHP Streams: http
> php
> ftp
> https
> comp
You may want to mention what the following means, this is
from a phpinfo() on www.php.net:
Registered PHP Streams: http
php
ftp
https
compress.zlib
Is there a function to get this specific informatio
> Please make that dir stream not streams as to make
> the shortcuts nicer for api vs function reference.
>
Half a step ahead of ya...
./en/reference/stream/reference.xml
./en/reference/stream/functions/stream-get-meta-data.xml
./en/reference/stream/functions/stream-register-wrapper.xml
./en/refer
> Yup, as I mentioned pollita on #php, a new dir
> "en/reference/streams" would be the best way to go.
>
> +1 for that addition.
Please make that dir stream not streams as to make
the shortcuts nicer for api vs function reference.
Regards,
Philip
--
PHP Documentation Mailing List (http://ww
> A major benefit of this new section will be having its
> own large introduction. This is much needed as it needs
> to be wordy, and include examples and comparisons of a
> few other "alternative/older" methods.
>
> I do not volunteer doing this as I don't understand the
> topic of streams yet bu
--- Derick Rethans <[EMAIL PROTECTED]> wrote:
> On Thu, 2 Jan 2003, Gabor Hojtsy wrote:
>
> > > Actually, turns out:
> > > stream_get_meta_data
> > > stream_register_wrapper
> > > stream_set_blocking
> > > stream_set_timeout
> > > stream_set_write_buffer
> > >
> > > ARE in the manual under the fi
On Thu, 2 Jan 2003, Derick Rethans wrote:
> On Thu, 2 Jan 2003, Gabor Hojtsy wrote:
>
> > > Actually, turns out:
> > > stream_get_meta_data
> > > stream_register_wrapper
> > > stream_set_blocking
> > > stream_set_timeout
> > > stream_set_write_buffer
> > >
> > > ARE in the manual under the filesys
IMHO, since streams have become such an integral part of PHP, it would
be best to create a full new section about them, and make links from all
other files to the new section...
- Tularis
Sara Golemon wrote:
Sounds appropriate to me. Looks like only streams
information exists for dev/api peopl
On Thu, 2 Jan 2003, Gabor Hojtsy wrote:
> > Actually, turns out:
> > stream_get_meta_data
> > stream_register_wrapper
> > stream_set_blocking
> > stream_set_timeout
> > stream_set_write_buffer
> >
> > ARE in the manual under the filesystem section. Should the missing
> > functions be added in the
> Actually, turns out:
> stream_get_meta_data
> stream_register_wrapper
> stream_set_blocking
> stream_set_timeout
> stream_set_write_buffer
>
> ARE in the manual under the filesystem section. Should the missing
> functions be added in there? Or still go ahead with creating a new streams
> section
>
> Sounds appropriate to me. Looks like only streams
> information exists for dev/api people currently:
>
> http://www.php.net/streams
>
> So in the end we will have php.net/streams going to
> the API docs and php.net/stream going to the
> function reference (ref.stream). Be sure to link
> eac
to you?
Andrey
- Original Message -
From: "Philip Olson" <[EMAIL PROTECTED]>
To: "Sara Golemon" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, January 02, 2003 9:26 PM
Subject: Re: [PHP-DOC] streams reference
>
> Sounds
Sounds appropriate to me. Looks like only streams
information exists for dev/api people currently:
http://www.php.net/streams
So in the end we will have php.net/streams going to
the API docs and php.net/stream going to the
function reference (ref.stream). Be sure to link
each to one anothe
((A questing in OPN/#php brought up the following issue))
So we've got all these streams in php now, but (for all I can tell) no
Streams section in the manual reference. Is anyone working on documenting
these already? Most functions seem to be ported versions of already
existing functions (socke
24 matches
Mail list logo
