celix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rlenfer...@apache.org
Subject [celix] branch develop updated: Fixed broken links in RSA description
Date Fri, 21 Jun 2019 17:11:19 GMT
This is an automated email from the ASF dual-hosted git repository.

rlenferink pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/celix.git


The following commit(s) were added to refs/heads/develop by this push:
     new 7ab6ad4  Fixed broken links in RSA description
7ab6ad4 is described below

commit 7ab6ad4beb299fc574f8f63719b27ff98973723b
Author: Roy Lenferink <lenferinkroy@gmail.com>
AuthorDate: Fri Jun 21 19:10:58 2019 +0200

    Fixed broken links in RSA description
---
 bundles/remote_services/README.md | 12 ++++--------
 1 file changed, 4 insertions(+), 8 deletions(-)

diff --git a/bundles/remote_services/README.md b/bundles/remote_services/README.md
index 8bd8bc7..b742270 100644
--- a/bundles/remote_services/README.md
+++ b/bundles/remote_services/README.md
@@ -102,17 +102,13 @@ To develop for the Remote Service Admin implementation of Celix, one
needs the f
 
 1. A service **interface**, describes the actual service and methods[^1] that can be called.
The service interface is needed at development time to allow a consistent definition;
 2. A service **implementation**, when exporting it as remote service. A service endpoint
is needed to delegate remote requests to your service implementation;
-3. A service **endpoint**, which will be installed by Celix when exporting a local service.
The endpoint is responsible for calling the actual Celix service. Endpoint bundles are not
needed when *only* importing services in Celix;
-4. A service **proxy**, which will be installed by Celix when importing a remote service.
The proxy is responsible for marshalling and unmarshalling method invocations. Proxy bundles
are not needed when *only* exposing services from Celix;
-5. A service **client** or user, which invokes methods on the local or remote service. The
client is oblivious to the fact whether the service is running locally or remote.
+3. A service **client** or user, which invokes methods on the local or remote service. The
client is oblivious to the fact whether the service is running locally or remote.
 
 The Celix source repository provides a simple calculator example that shows all of the described
parts:
 
-1. [The calculator service interface](http://svn.apache.org/repos/asf/celix/trunk/remote_services/calculator_service/public/include/calculator_service.h),
providing three methods: one for adding two numbers, one for subtracting two numbers, and
lastly, a method that calculates the square root of a number;
-2. [A calculator service implementation](http://svn.apache.org/repos/asf/celix/trunk/remote_services/calculator_service/private/src/calculator_impl.c)
that simply implements the three previously described functions. To mark this service as "remote
service", you need to add the `service.exported.interfaces` service property to its service
registration. This way, the RSA implementation can expose it as remote service to others;
-3. [A service endpoint](http://svn.apache.org/repos/asf/celix/trunk/remote_services/calculator_endpoint/private/src/calculator_endpoint_impl.c),
which is called by the RSA implementation to delegate a method invocation to an actual method
in the service implementation. The service endpoint should be registered as `remote_endpoint`
service, along with the `remote.interface` service property denoting which service interface
this endpoint is capable of handling;
-4. [A service proxy (factory)](http://svn.apache.org/repos/asf/celix/trunk/remote_services/calculator_proxy/private/src/calculator_proxy_impl.c),
called by the service client when it wants to invoke a method on a remote service. The service
proxy should be registered as `remote_proxy_factory` service along with the `proxy.interface`
service property denoting which service interface the service proxy is capable of handling;
-5. [A service client](http://svn.apache.org/repos/asf/celix/trunk/remote_services/calculator_shell/private/src/add_command.c),
that exposes the three calculator methods to as Celix shell commands. The implementation simply
retrieves the calculator service as it would do with any other Celix service.
+1. [The calculator service interface](https://github.com/apache/celix/blob/develop/bundles/remote_services/examples/calculator_api/include/calculator_service.h),
providing three methods: one for adding two numbers, one for subtracting two numbers, and
lastly, a method that calculates the square root of a number;
+2. [A calculator service implementation](https://github.com/apache/celix/blob/develop/bundles/remote_services/examples/calculator_service/src/calculator_impl.c)
that simply implements the three previously described functions. To mark this service as "remote
service", you need to add the `service.exported.interfaces` service property to its service
registration. This way, the RSA implementation can expose it as remote service to others;
+3. [A service client](https://github.com/apache/celix/blob/develop/bundles/remote_services/examples/calculator_shell/src/add_command.c),
that exposes the three calculator methods to as Celix shell commands. The implementation simply
retrieves the calculator service as it would do with any other Celix service.
 
 If you have access to the Celix source repository, you can run the calculator example using
various discovery implementations by invoking the `deploy` target. You can find the example
deployments in the `CELIX_BUILD/deploy` directory. For example, to run the calculator example
using the configured discovery mechanism, you should open two terminals. In the first terminal,
type:
 


Mime
View raw message