From: Karl R. <rk...@vr...> - 2002-02-23 00:50:33
|
> 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/ could you pass N when setting up the AppNode in your .conf? this wouldn't help if you wanted each thread to do down a different path, i guess. unless you could treat the CRAppliocationNode as an array and assign a spu chain to each. but that would still require hard-coding in the number of threads, which is a bit hacky.. but im not sure how the mothership would find this out, short of making the application register each thread with the mship. though that would introduce all sorts of ordering problems (if the crserver was started before crappfaker), unless the mothership started jobs up.. a more robust spu network configurer would be nice, especially if applications could query/set it themselves. though keeping each node in sync with the current configuration could be a bear. karl [k a r l r a s c h e] the math department makes me feel normal -- campus grafiti rk...@vr... |