http://www.sidefx.com/index.php?option=com_forum&Itemid=172&page=viewtopic&t=9672&highlight= [sidefx.com]
Error codes would be good, but that's not the point - i want tobut how would you avoid this if the ticketing system issues ticket 0 (when there is no more licenses). Is it not equivalent of obtaining a return code that indicates there is no licenses? You still need to retry to obtain ticket (instead of retrying to start a render)
avoid all this, but it requires SideFx to participate.
Perhaps we are not envisioning the same mechanics of the rendering supervision system. What I was thinking about is that a render node starts a render and if it failed to obtain a license, it would inform the dispatcher about the license failure (much like obtaining a zero ticket). Then the dispatcher would wait a second or two and retry the same (or the next) job (again, like waiting a second and polling the server for a ticket).
The only difference between the return code and ticketing systems is that the dispatcher obtains the licensing availability information from the render node rather than directly from the license server.
Perhaps requeing or resending the job consumes bandwith (or other resources), in which case the render node could store the render data for the failed job and the dispatcher would only need to send a signal to “go ahead and try again” (or “abort altogether”, if need be).