MCPcopy Create free account
hub / github.com/apache/dubbo-go / RPCInvocation

Struct RPCInvocation

protocol/invocation/rpcinvocation.go:39–55  ·  view source on GitHub ↗

todo: is it necessary to separate fields of consumer(provider) from RPCInvocation RPCInvocation carries method, parameters, attachments and invocation metadata.

Source from the content-addressed store, hash-verified

37// todo: is it necessary to separate fields of consumer(provider) from RPCInvocation
38// RPCInvocation carries method, parameters, attachments and invocation metadata.
39type RPCInvocation struct {
40 methodName string
41 // Parameter Type Names. It is used to specify the parameterType
42 parameterTypeNames []string
43 parameterTypes []reflect.Type
44
45 parameterValues []reflect.Value
46 parameterRawValues []any
47 arguments []any
48 reply any
49 callBack any
50 attachments map[string]any
51 // Refer to dubbo 2.7.6. It is different from attachment. It is used in internal process.
52 attributes map[string]any
53 invoker base.Invoker
54 lock sync.RWMutex
55}
56
57// NewRPCInvocation creates a RPC invocation.
58func NewRPCInvocation(methodName string, arguments []any, attachments map[string]any) *RPCInvocation {

Callers

nothing calls this directly

Calls

no outgoing calls

Tested by

no test coverage detected