Re: Re: Re: [PHP] Full-Duplex communication

2002-05-22 Thread Evan Nemerson
You're right- this is getting interesting ;) http://www.packetfactory.net/libnet/manual/4.html#s4.1.5 Unless I'm mistaken, you don't need to actually hijack the socket- you merely need to write to the network. Check out section 3.1 of RFC 793. There is source and destination port- that is how

Re: Re: Re: [PHP] Full-Duplex communication

2002-05-22 Thread Richard Archer
At 7:01 AM + 22/5/02, Vinod Panicker wrote: >What i have at the other end is a Instant Messenger client :) Which is presumably accepting some form of HTML or at least a stream of data sent over HTTP and displaying the data. If it's notdoing this, Apache is almost certainly the wrong platfor

Re: Re: Re: [PHP] Full-Duplex communication

2002-05-21 Thread Vinod Panicker
What i have at the other end is a Instant Messenger client :) Cant have the script running till the time the user logs out can i? And also, different activities are triggered on the server asynchronously (presence status, instant messages, notifications) which has to be sent to the client. T

Re: Re: Re: [PHP] Full-Duplex communication

2002-05-21 Thread Vinod Panicker
Thanks for the reply Miguel, but here i'm not trying to implement my own multi-threaded server - exactly the reason why i'm using Apache / PHP. I could have made a listening server which is based on a multi-threaded or multi-forked model, but the time and complexities involved would be huge.