-
Notifications
You must be signed in to change notification settings - Fork 99
Add support for symbol based serialization/RPC #85
Copy link
Copy link
Open
Labels
component/pubsubCategorizes an issue or PR as relevant to pubsub.Categorizes an issue or PR as relevant to pubsub.component/remote-servicesCategorizes an issue or PR relevant to remote services.Categorizes an issue or PR relevant to remote services.kind/improvementCategorizes issue or PR as related to improvements.Categorizes issue or PR as related to improvements.
Milestone
Description
Metadata
Metadata
Assignees
Labels
component/pubsubCategorizes an issue or PR as relevant to pubsub.Categorizes an issue or PR as relevant to pubsub.component/remote-servicesCategorizes an issue or PR relevant to remote services.Categorizes an issue or PR relevant to remote services.kind/improvementCategorizes issue or PR as related to improvements.Categorizes issue or PR as related to improvements.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Currently the remote service admin and pubsub are based on the use of dfi and descriptors. Another option could be to support the de/serialization and RPC using predefined function signatures.
Using the extender pattern these function can be found and used without polluting the types/services with serialization/RPC code and make it possible to support a wide range of existing serialization/rpc techniques.
For example a service with the name "HelloWord" could have a bundle entry 'META-INF/services/HelloWorld.rpc_info' entry containing a simple properties files with - atleast- the entires "create_proxy" and "create_endpoint". These refer to symbols in the shared libraries of the bundle with predefined signatures.
More design details are needed before this can be implemented. Also a initial tech. should be chosen (e.g. RPC).
Original creation date: 09/Apr/2018
Reporter: @pnoltes