2010/2/22 Iustin Pop <[email protected]>: > The problem is that any non-CLI client that uses luxi will have to > handle this by itself, which is a no-go; we don't want to require use of > cli.py always. > > On the other hand, no-one is using directly luxi.WaitForJobChange.... > but if we need to, in the future, then we should re-add the loop in > luxi. > > Maybe adding a separate method 'CheckForJobChange', that does > self.CallMethod(), and then add in luxi itself the wrapper > 'WaitForJobChange'?
My proposal in that case is to leave WaitForJobChange's behaviour as it is, and add a new function, e.g. WaitForJobChangeOnce, which is in turn used by WaitForJobChange (a variation of your proposal). What do you think? Regards, Michael
