I feel like kicking myself! Forgot all that I had learnt abt sockets! What I actually wanted was the ability to use the socket from another process. I obviously cant do that in this case since the socket that has been opened is local to the process (DUH!)
Now I want to pass this socket to another application, which can write to it when required. I'm sitting with stevens right now, hunting for ways in which I can pass open file descriptors to another process :) Any help would be welcome. I don't require the input filters, since I want to write to the socket of a keep-alive connection later. Was just wondering if I can do it in a simple way, or I'll have to use libnet to do it Tx, Vinod. ----------------------------------- Vinod Panicker <[EMAIL PROTECTED]> Sr. Software Designer Geodesic Information Systems Ltd. -----Original Message----- From: Sander Striker [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 30, 2002 2:54 PM To: [EMAIL PROTECTED]; Vinod Panicker Subject: RE: Client socket > From: Tony Finch [mailto:[EMAIL PROTECTED]]On Behalf Of > 'Tony Finch' > Sent: 30 May 2002 11:01 > On Thu, May 30, 2002 at 11:03:05AM +0530, Vinod Panicker wrote: > > > > I need the actual socket that apache uses to communicate with the > > client in the php module. Is it available somewhere in the > > request_rec structure? > > You've already found it in r->connection->client->fd. Question: why do you need the socket? Staying away from the socket is in general a better idea. You get all the data through the input filters, bypassing those means you lose out on a lot of functionality. Sander
