From: Brian P. <br...@tu...> - 2002-02-22 23:56:57
|
(this is mostly a question for Greg) My current problem in the multithread work is making the crserver (and mothership) accept more client connections after initialization. The idea is that a client may create N threads and each should appear to the server as a separate client. For example, the psubmit demo currently works by starting N client processes which use a downstream render SPU on the server. In the future, we'd like to be able to run one instance of the psubmit program that creates N threads. Again, those N threads should appear as N separate clients to the server. The problem is that the server and mothership look at the SPU graph to determine how many clients there are for each server and assume that the number won't change. I'd like to be able to add more clients later. I'm still learning my way around the spu/server communication code. It appears that after initialization, the server goes into the crServerSerializeRemoteStreams() loop and there's no way to setup another client after that point. I don't think updating the server's data structures is really the problem - it's moreso the brokering/ negotitions that take place between the spu and server that seems to be the problem. Any tips on how to accomplish this would be appreciated. -Brian |