ADTF  3.15.3
IRPCObjectServerabstract

The RPC Object Server Interface defines the basics to receive RPC calls. More...

Inheritance diagram for IRPCObjectServer:
[legend]

Public Member Functions

 ADTF_IID (IRPCObjectServer, "rpc_object_server.ant.services.adtf.iid")
 ADTF IID Defintion.
 
virtual tResult Receive (const base::ant::IRawMemory &oRequest, base::ant::IRawMemory &&oResponse)=0
 Implement to receive RPC requests. More...
 
virtual tResult GetRPCIID (base::ant::IString &&strIID) const =0
 
virtual tResult GetRPCName (base::ant::IString &&strRPCName) const =0
 
virtual tResult SetRPCName (const char *strRPCName)=0
 
- Public Member Functions inherited from IObject
 ADTF_IID (IObject, "object.ant.ucom.adtf.iid")
 Marks the IObject to be castable with the ucom_cast() More...
 

Protected Member Functions

 ~IRPCObjectServer ()=default
 hidden ctor
 
- Protected Member Functions inherited from IObject
 ~IObject ()=default
 Protected destructor --> Use implemented Destroy() instead of delete!
 

Detailed Description

The RPC Object Server Interface defines the basics to receive RPC calls.

This Interface is used to register to adtf::services::ant::IRPCObjectServerRegistry.

Definition at line 27 of file rpc_object_server_registry_intf.h.

Member Function Documentation

◆ Receive()

virtual tResult Receive ( const base::ant::IRawMemory oRequest,
base::ant::IRawMemory &&  oResponse 
)
pure virtual

Implement to receive RPC requests.

The content of oRequest and oResponse is depending on the used protocol.

Parameters
[in]oRequestRequest message
[in,out]oResponseResponse message (use i.e. adtf_memory_intf)