On 2001-02-27 20:07:09, Andi Gutmans wrote:
> Do you have time to map where in PHP we are currently using socket code?
> I think according to how many places and how we are using it, it'll help us
> decide how much redesigning we can do. Also keep Win32 in mind while
> thinking of this.
As is
Do you have time to map where in PHP we are currently using socket code?
I think according to how many places and how we are using it, it'll help us
decide how much redesigning we can do. Also keep Win32 in mind while
thinking of this.
I didn't have much time but I did read through your RFC quic
On Mon, Feb 26, 2001 at 11:39:51PM +, Wez Furlong wrote:
> When opening a socket there are 3 stages (and thus operations on the socket):
>
> 1. Create a socketd of appropriate domain/type/family (socket(2))
> 2. resolve the address to connect to (domain specific)
> 3. make the connection (con
On 2001-02-26 08:21:23, Stig Venaas <[EMAIL PROTECTED]> wrote:
> Sounds good to me. It's also impossible in a portable way to know if a
> socket is AF_INET, AF_INET6 or AF_LOCAL, so for socket() function etc.
> I've been thinking of doing something like this to store what domain
> a socket is
On Mon, Feb 26, 2001 at 01:31:05AM -, Wez Furlong wrote:
> I've been reviewing my relatively crude patch from September last year that
> provided transparent SSL socket access to PHP via the php functions
> fsockopen, fread etc. etc.
Great, I was wondering what happened, was considering doing
I've been reviewing my relatively crude patch from September last year that
provided transparent SSL socket access to PHP via the php functions
fsockopen, fread etc. etc.
It would be very simple to integrate this into the current PHP code base,
but to do so I think we would need to make some modi
