_ms_dispatch() is the only caller, and it is confusing to have both
dispatch() and dispatch_op() that take the same argument type.
Signed-off-by: Sage Weil <sage@redhat.com>
}
MonOpRequestRef op = op_tracker.create_request<MonOpRequest>(m);
- dispatch(op);
-}
-
-void Monitor::dispatch(MonOpRequestRef op)
-{
- op->mark_event("mon:dispatch");
+ op->mark_event("mon:ms_dispatch");
ConnectionRef connection = op->get_connection();
MonSession *s = NULL;
MonCap caps;
reuse_caps = true;
s = NULL;
}
- Message *m = op->get_req();
if (!s) {
// if the sender is not a monitor, make sure their first message for a
// session is an MAuth. If it is not, assume it's a stray message,
lock.Unlock();
return true;
}
- // dissociate message handling from session and connection logic
- void dispatch(MonOpRequestRef op);
void dispatch_op(MonOpRequestRef op);
//mon_caps is used for un-connected messages from monitors
MonCap * mon_caps;