Well,
It is possible to make an Android version of River, with substituted
java.rmi.* classes, that is compatible with java, provided that the
serial from of those classes is identical to the java versions,
including the serialized class name, then yes, it is possible. But it
will still require a different codebase annotation schema, it could be
as simple as a codebase server that has *.jar and *.aar files with the
same name, but the android client version substitues *.jar with *.aar in
the stream's codebase annotations.
Maybe it's not so hard after all.
Regards,
Peter.
On 14/06/2015 11:28 AM, Peter wrote:
Dawid,
It's possible, but:
1. It requires breaking changes to replace java.rmi.* classes (mostly
interfaces and exceptions).
2. A codebase annotation schema that allows different client
platforms to select the correct codebase for their platform.
Then, yes we could have a platform that supports both Java and
Android, however it wouldn't be backward compatible with Jini.
The challenge isn't technical, the challenge is getting the community
on board.
Hi All,
Peter Firmstone obviously looked at this about 5 years ago, and even
raised a support question
<https://groups.google.com/forum/#%21topic/android-platform/mxCM91oQDjo>
with Google in terms of
making certain java.rmi.* classes available on the platform.
I was wondering, has anything happened since then? What are the
prospects of getting River to work on the Dalvik VM?
I imagine there are many potential issues around code downloading
(classloading) and security, but the mobile devices world is ripe for
River, or something like it.
warm regards,
Dawid Loubser
