The existing name is confusing, hard to remember and makes little sense.
Schedulers deserve a more memorable name, because this is the main object they use for managing open requests.
The ResourceRequest class plays a similar role for requesters. That name seems OK.
I would like to call it something similar to SchedulerRequest, but that is confusingly close to the scheduler_msgs/SchedulerRequests message. Maybe an abbreviated SchedReq would do, although I generally dislike abbreviations.
Maybe OpenRequest would work, despite the fact that they do spend some time in the CLOSED state.
The existing name is confusing, hard to remember and makes little sense.
Schedulers deserve a more memorable name, because this is the main object they use for managing open requests.
The
ResourceRequest
class plays a similar role for requesters. That name seems OK.I would like to call it something similar to
SchedulerRequest
, but that is confusingly close to thescheduler_msgs/SchedulerRequests
message. Maybe an abbreviatedSchedReq
would do, although I generally dislike abbreviations.Maybe
OpenRequest
would work, despite the fact that they do spend some time in the CLOSED state.I am open to better ideas. Suggestions?