Hi Nick, > 1). Port Listener > 2). Virtual Directory traffic manager > 3). Worker process/thread
> In the above scenario would there be any advantage to using your proper multithreading as opposed to the above? No, even Microsoft uses separate EXEs for different virtual directories or application domains, depending on how you configure the web server. However, there're two issues you need to deal with: 1) If the worker thread should run as a different thread than the traffic manager, you need the C++ helper to create the COM object in a different thread. Otherwise, all worker threads are created in the main thread. Check _VFP.ThreadID to make sure how many threads you actually have. 2) Depending on how you pass information, you need to be aware of call blocking. If each component uses COM to call the next one, your port listener is blocked when the first request comes in. With named pipes you would have to use asynchronous IO to keep the pipe open while the port lisnter waits on ports and pipes. That's why I would implement this module in C++. The listener would respond to the socket request, spwan a new thread which would use regular named pipes to directly communicate with the worker thread. -- Christof _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
