SpringCloud/spring-cloud-function
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

GH-744 Add default port note to gRPC README

Browse Source
This commit is contained in:
Oleg Zhurakousky
2021-09-27 15:53:27 +02:00
parent 3a989e6b5a
commit 63a5678f26
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
spring-cloud-function-grpc/README.md
View File

@@ -19,6 +19,9 @@ only be interested in client-side utilities to invoke a function exposed via gRP
To support these two modes Spring Cloud Function provides `spring.cloud.function.grpc.server` which defaults to `true`.
This means that the default mode of operation is _server_, since the core intention of our current gRPC support is to expose user Functions via gRPC. However, if you're only inteersted in using client-side utilities (e.g., `GrpcUtils` to help to invoke a function or convert `GrpcMessage` to Spring `Message` and vice versa), you can set this property to `false`.
In the server (default) mode, te gRPC server would be bound to te default port ***6048***. You can change it by providing
`spring.cloud.function.grpc.port` property.
#### Core Data and Service
At the center of gRPC and Spring Cloud Function integration is a canonical protobuff structure - `GrpcMessage`. It is modeled after Spring [Message](https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/messaging/Message.html).