I have developed remote method call library for Windows. Basically you write a service contract interface, and create a generic consumer or provider of the interface. Using transparent proxy the consumer method call is then serialized and sent to the provider (transparently behind the scenes). The provider then deserializes and uses transparent proxy to delivery those method calls to an instance of the contract interface. And of course the method response value (or exception) results in another movement of data over the wire. For the consumer the contract interface object instance is used in the same way as a local class/object to call methods and receive events.
If anyone has published library work similar to this already I have not seen it. I suspect this will be a deep dive into reflection and B4A/Java interop to get to those important proxy invokes. I don't even know if this is possible via B4A classes. I like the "transparent" aspect as it hides so many messy implementation details from the user and hope to be able to leverage that with B4A if possible.
Seeking any wisdom or pointers before digging in here. Forget it, not possible is a valid response.
If anyone has published library work similar to this already I have not seen it. I suspect this will be a deep dive into reflection and B4A/Java interop to get to those important proxy invokes. I don't even know if this is possible via B4A classes. I like the "transparent" aspect as it hides so many messy implementation details from the user and hope to be able to leverage that with B4A if possible.
Seeking any wisdom or pointers before digging in here. Forget it, not possible is a valid response.