There are two life cycles of RPC call i.e. Unary RPC and Streaming RPC .
gRPC supports unary RPC and three types of streaming RPC :
Client Side Streaming 2. Server Side Streaming 3. Bidirectional Streaming
The gRPC parser is considered complete only when it supports both unary and streaming RPC calls.
Why should this be worked on?
As for now , only the unary RPC feature had been implemented in the gRPC parser of keploy's integrations .
But as unary RPC are not the ideal case everywhere so the streaming RPCs should also be supported to make gRPC parser feature-rich.
Is there an existing feature request for this?
Summary
There are two life cycles of RPC call i.e. Unary RPC and Streaming RPC . gRPC supports unary RPC and three types of streaming RPC :
Why should this be worked on?
As for now , only the unary RPC feature had been implemented in the gRPC parser of keploy's integrations . But as unary RPC are not the ideal case everywhere so the streaming RPCs should also be supported to make gRPC parser feature-rich.
Repository
keploy