Tracking Issue for (Call|ServerCall)StreamObserver being Experimental.

[carl-mastrangelo]

Specific usages:

• CallStreamObserver
• ServerCallStreamObserver

[wu-sheng]

The ClientCallStreamObserver and CallStreamObserver have be annotated by @ExperimentalApi. Can you tell me why?

Is the api good enough to use on product env. ? This API is very useful for our project. But I need grpc-team to confirm.

Thanks. @ejona86

[ejona86]

The APIs are functional but we still reserve the right to change the API. Once there have been some users and agreement that the APIs are working well then we would remove the annotation.

I'm not quite settled with disableAutoInboundFlowControl, for example, because it still has an implicit request() when the RPC starts. The basic functionally it provides is likely to stay (since flow control is essential) but the precise form can change.

[vkedia]

@ejona86 Do you have any further updates on making this non experimental? We use this API in the cloud spanner client library and it has worked well for us so far. But this being experimental prevents our client from going GA.

[ejona86]

@vkedia, no I don't. This depends on stabilizing ClientCallStreamObserver and I think there are some issues that need to be resolved for client vs server APIs.

[ejona86]

API discussion notes for disableAutoInboundFlowControl:
General agreement that a different name would make the API easier to understand and worth converting existing users. Although not important enough by itself, removing the special case on unary would be good. Since we're wanting a new name, also remove unary special case.

Names:
disableAutoInboundFlowControl
disableAutoRequest +1 +1
disableImplicitRequest
useExplicitRequest
setAutoRequest(false) +1 +1

I'm interested in eventually adding the auto/implicit request() calls to ClientCall/ServerCall (but it would be opt-in). That influenced people's preference for name (e.g., moved a vote from useExplicitRequest to setAutoRequest)
useImplicitRequest
enableAutoRequest
enableImplicitRequest
setAutoRequest(true)

No clear winner. Will loop back around to it.

[carl-mastrangelo]

requestOnMessage?