RE: [PHP-DEV] Re: Client socket

I'm no apache expert when it comes to hacking the source or anything, but it appears that ap_rwrite() and ap_write() might do what you're looking for. They look something like this: int ap_rwrite(const void *buf, int nbyte, request_rec *r); And apparently they let you write directly to the request. Or something like that. J Vinod Panicker wrote: > Makes sense. Dunno why it didn't occur to me before - the '3' says it > all. > > I need the actual socket - which when written to will send data to the > client. Is it there in the request_rec structure? > > Or can I get it some other way? > > Tx, > Vinod. > > ----------------------------------- > Vinod Panicker <vinod@geodesiconline.com> > Sr. Software Designer > Geodesic Information Systems Ltd. > > > > -----Original Message----- > From: J Smith [mailto:dark_panda@hushmail.com] > Sent: Wednesday, May 29, 2002 8:13 PM > To: php-dev@lists.php.net > Subject: [PHP-DEV] Re: Client socket > > > > Since apache is multi-processed rather than multi-threaded, I'd imagine > that > you're getting the same socket file descriptor since each new connection > > means a new fork of httpd, resulting in three file descriptors by the > time > you get to what you're doing. > > Are you trying to get ahold of the socket/port number itself? Or connect > to > the actual socket? > > J > >