How did you implement it? The main problem with doing this until now was
that under Windows, it's pretty much impossible to get a FILE* from a
socket. The right way to implement it would most probably be implementing
something similar to C++'s virtual classes, so I'm wondering whether you
did it that way...
Zeev
At 19:22 17/4/2001, Wez Furlong wrote:
>On 2001-04-17 16:26:19, "Hartmut Holzgraefe" <[EMAIL PROTECTED]> wrote:
>
> > Wez Furlong wrote:
>
> > > I'm working on a file abstraction for fopen and friends,
>
> > > with the aim of nuking all those issock parameters
>
> > > and paving the way so that I can finally integrate
>
> > > SSL support for those functions.
>
> >
>
> > Would that be something as general as the GLIBC fopen cookies?
>
>
>
>It borrows from that idea, but has to work without them. It takes
>advantage of fopen cookies is available by allowing you to "cast" the
>stream into a FILE* regardless of whether it's an fd, socketd, FILE*, SSL
>socket, memory based stream or whatever.
>
>
>
>I'm on the verge of checking-in my work-so-far (it can be enabled by
>--enable-php-streams) so that others can try it and comment. In
>particular, I would like someone who knows buffers to review the buffering
>- I've borrowed code from fsock.c but it looks like a memory hog to me,
>and doesn't allow buffered writes.
>
>
>
>--Wez
--
Zeev Suraski <[EMAIL PROTECTED]>
CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
