This archive is the source code of OpenCV Manger which refer to OpenCV tutorial,implemented by Java,on the android platform.
I have been coding an platform recently, which can manage library binaries on end users devices, such as android, iOS and so on.
The platform can be regarded as a Service Store, which is just like the app store in android, where delelopers develop their own apps and deploy them onto the app store, and users can download the app that they like and install it on his or her devices. Therefore, android's app store can be treated as an ecological system.
However, our Service Store is also an ecological system, where the Service Manufacture or Lib Developers can develop their own Cloud Services or Native Services, and users can connect to the service they like on their end devices, e.g. Voice Recognition Service, Face Detection Service, etc. The technical architecture of the platform is shown below.
Technical Architecture
On Andrioid platform, it provides AIDL for developers. AIDL (Android Interface Definition Language) is similar to other IDLs you might have worked with. It allows you to define the programming interface that both the client and service agree upon in order to communicate with each other using interprocess communication (IPC). On Android, one process cannot normally access the memory of another process. So to talk, they need to decompose their objects into primitives that the operating system can understand, and marshall the objects across that boundary for you. The code to do that marshalling is tedious to write, so Android handles it for you with AIDL. With AIDL, developers don't need to know the underlying Binder mechanisms.
Refer to the OpenCV Manager Manual. Just like the OpenCV Manager, the Engine Manager is also an Android service targeted to manage OpenCV library binaries on end users devices. It allows sharing the dynamic libraries between applications on the same device, such as Face Detection lib, Voice Recognition lib. The Engine Manager provides the following benefits:
- Less memory usage. All apps use the same binaries from service and do not have to keep the native libs inside themselves;
- Hardware specific optimizations for all supported platforms, such as the different CPU-Arch of Android platform;
- Once the Engine is released, all the Service Libraries will be trusted library source. All packages with OpenCV should be published on Google Play market or Apple's App Store;
- Regular updates and bug fixes;
To know the usage of the third-party libs, I designed a JSON-like formatted config file, which contains some pairs of key-values. It supports following mechanisms:
- Key-Values. The config file is JSON-like formatted, so it is composed of pairs of key-values;
- Inheritance mechanism. Since the third-party libs are usually object-oriented, inheritance mechanism can effectively reduce the trouble of writing the config files;
- Induction mechanism. To support the feature of inheritance mechanism, we can include the config file from the outside files;
- Comments. For the purpose of readability, I think the config file should support comments.
Implemented by flex & bison, it is able to describe the usage of the third-party libs on Android platform, which is suffixed by .so, .a, .o, etc.