grpc::ServerUnaryReactor - Callback processing

[Brent Edwards]

I am trying to implement grpc callback service and have derived my callback handler class from ServerUnaryReactor.

class AuthorisationCallbackHandler : public grpc::ServerUnaryReactor

As part of request processing we return grpc::ServerUnaryReactor to grpc server/service.

The destructor for AuthorisationCallbackHandler is never called so I assume we are still responsible for its clean up.

Is this correct and how to we know grpc is finished with it?

Is that what grpc::ServerUnaryReactor::OnDone is for?

[Viktor Khristenko]

Hi ,

Check these cpp examples: https://github.com/grpc/grpc/blob/master/examples/cpp/route_guide/route_guide_callback_server.cc#L159

It's for streaming, but the same idea applies. 

Also note that you could use default reactor for unary calls (unless you really need to impl your own one).

`ctx->DefaultReactor()`, then you do not have to worry about this clean up. Although this applies only for unary calls, but this is what you are asking for...

In short, you can delete after OnDone was triggered for server reactor

Hope that helps!

VK