On 11/3/06, <b class="gmail_sendername">Phil Mayers</b> <<a href="mailto:p.mayers@imperial.ac.uk">p.mayers@imperial.ac.uk</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Yi Qiang wrote:<br>> This is the part where I stumble on though, the exact implementation of<br>> how to make it so that one calls back the other.<br><br>One what calls back the other what?<br><br>You'll have issues with error handling and dropping workers if you're
<br>not careful to chain the deferreds correctly. I would try something like<br>this personally. ...</blockquote><div><br>Hi Phil,<br>Sorry it took me so long to get back to you. Thanks for your suggestion, but the thing I was trying to avoid is to have the Workers communicate with the PB server. There could be potentially many workers and when I thought about the problem, it seemed cleaner to design something where the client consisted of a 'Monitor' and 'Workers'. The monitor connects to the server, gets jobs, distributes jobs to the workers and watches for workers who finished their jobs. What do you think of this design? It is obviously a little more convoluted to program but might be easier to deal with in the future. I have little programming experience so this is all speculation from my side. Any insight would be greatly appreciated.
<br></div><br><div>Thanks,<br>Yi<br> </div></div><br>