|
ADTF
|
| Plugin Filename | adtf_core.adtfplugin |
|---|---|
| Plugin Description | adtf_core.plugindescription |
| Plugin Name | ADTF Core Plugin |
| License | ADTF Subscription |
| Support Mail | support@digitalwerk.net |
| Homepage URL | https://adtf.dev |
| Plugin Version | 3.99.99 |
|---|---|
| Plugin File Version | 1.0 |
| adtf | 3.99.99 |
| adtf::ucom | 3.1.0 |
| Name | RPC Object Server Registry |
|---|---|
| CID | rpc_object_registry.service.adtf.cid |
| Description | The internal RPC server. |
| Type | Service |
| Default Runlevel | system |
| Name | Value | Type | Description | Subproperties |
|---|---|---|---|---|
| url | cString | The url that defines how and where to listen for RPC calls. | Value Range: minimum = maximum = Filename Extension Filter: |
The RPC Object Server Registry is a single instance to create a single adress entry for RPC Server Objects.
The registered object by adtf::services::IRPCObjectServerRegistry will be reached via the same adress as the registry itselve.
Within the ADTF Launcher the communication is a simple JSON protocol: The registry is implemented as a JSON server by the given URL like http://localhost:8000.
Each Server object is reachable by a URL like http://localhost:8000/<objectname> given at strObjectName.
The rpc interface makes it possible to connect and interacte with an ADTF System / ADTF Launcher.
One powerful client is the ADTF Control.
See also adtf::remote and the external rpc package content within dev_essential.