>Yes, that's exactly what I want to do.  But HOW do I do it?
>
>i.e.  I'm sitting in my accept connectinos loop in the chat daemon
>
>While(true)
>{
> //waitforenwconnection
> $new_connection_id=socket_accept();
>
> //got a new connection, go process it
> go_do_this_in_a_new_thread($new_connection_id);
>}
>
>What do I put in place of go_do_this_in_a_new_thread()????

Use fsockopen() to "talk" to your *OTHER* PHP script waiting in a loop to do
the *real* work.

IE, have a *second* PHP file that runs on yet another socket to do the work.

>
>-----Original Message-----
>From: Demitrious S. Kelly [mailto:[EMAIL PROTECTED]] 
>Sent: Monday, July 22, 2002 3:01 PM
>To: 'David Buerer'; [EMAIL PROTECTED]
>Subject: RE: [PHP] Windows NT Server, FORK, SOCKETS, and seperate processes
>
>
>Yes. Write a daemon which listens on a socket and manages the communications
>it gets from the satellite scripts and works the database for them...
>
>The scripts send off data, and process replies. They don't do the heavy
>work...
>
>-----Original Message-----
>From: David Buerer [mailto:[EMAIL PROTECTED]] 
>Sent: Monday, July 22, 2002 2:30 PM
>To: '[EMAIL PROTECTED]'
>Subject: RE: [PHP] Windows NT Server, FORK, SOCKETS, and seperate processes
>
>How to I inovoke a new Thread from the middle of a PHP script?
>
>-----Original Message-----
>From: Paul Maine [mailto:[EMAIL PROTECTED]] 
>Sent: Monday, July 22, 2002 10:08 AM
>To: David Buerer; [EMAIL PROTECTED]
>Subject: RE: [PHP] Windows NT Server, FORK, SOCKETS, and seperate processes
>
>
>You can use threads with NT to accomplish what you are asking.
>
>-----Original Message-----
>From: David Buerer [mailto:[EMAIL PROTECTED]]
>Sent: Monday, July 22, 2002 11:29 AM
>To: '[EMAIL PROTECTED]'
>Subject: [PHP] Windows NT Server, FORK, SOCKETS, and seperate processes
>
>
>I've got effectivly a glorified chat server which upon the arrival of a
>message thorugh a socket connection goes off and runs a bunch of database
>processed.  My questions is this:  How can I seperate the database
>processing into a seperate processor process?  I really don't want the chat
>server to have to wait until after the database processing is done to go
>intercept and process another request--this just doesn't seem right.  I want
>the chat server process to be able to deal with getting and receiving
>messages, and another process to deal with the database processing. That way
>if one of the processes get's slow, the other isn't affected. Something like
>the fork command would work really well, but fork doesn't exist in NT.
>
>Anyone have any ideas?
>
>I'm running Windows NT4.0 sp6a
>Apache Server 1.3.xx
>MySQL
>and of course, PHP 4.2.1
>
>


-- 
Like Music?  http://l-i-e.com/artists.htm


-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to