On Tue, Aug 24, 2010 at 18:36, Michael Hanselmann <[email protected]> wrote: > Am 24. August 2010 18:33 schrieb Iustin Pop <[email protected]>: >> On Tue, Aug 24, 2010 at 18:30, Michael Hanselmann <[email protected]> wrote: >>> Yes, it needs to be a new call (unless there's a priority per opcode, >>> see above). The current call to submit opcodes, “SubmitJob” has an >>> interface equivalent to the Python code “def SubmitJob(*args)”. It >>> can't take anything but opcodes. >> >> True, but I very much dislike adding two new calls (remember that we >> also have submit multi job). > > I had forgotten about SubmitManyJobs—my bad. The new call could > combine both. They're not that different and can easily be abstracted > in the client.
True, in the client, but not at protocol level. >> I think we need to discuss first better >> the difference between per-opcode operation importance and the fact >> that we can have priorities only for jobs first. > > Sorry, do you mean that we should have per-opcode priorities? I just mean that I think we need to discuss this more, before committing on a design. Whether this thread is or isn't the best venue for this discussion I don't know :) iustin
