On Thu, Oct 10, 2013 at 03:01:33PM -0700, Gordon Leland Hempton wrote: > > No worries about keeping it meta. Part of this question was just to > establish that what I was doing was sane and that there wasn't some > obviously better way of doing things. > > I feel as though reserving workitems from a "queue-like" storage > participant would be an extremely common scenario and am surprised there > aren't more storage participant methods to this effect (e.g. something as > simple as a method to return unreserved workitems).
I just went for the most common scenario (imho) "engine assignes work to participant A". The reserve/owner thinggies came afterward. Since they got introduced, you're the first to request such a method. I guess it would be simple to add it. So your best practice question boils down to "please add a list_workitem_whose_owner_is_nil" request? Best regards, -- John Mettraux - http://lambda.io/jmettraux -- -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en --- You received this message because you are subscribed to the Google Groups "ruote" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
