I understand that android has limitation on sharing USB between PC and phone. We had the same problems in the early days of pre-windows type OS's where we were trying to create applications that ran on the same PC but under different instances (i.e. like VM) and had to share information and status between them. (yes - I am an old IT geezer)
In our limitations, we were assured that only 1 app would be running at a time and that the apps would be automatically switched by an external environmental control so an app might not have finished what it was doing and so had to log progress.
Our approach was to find a common disk location where the two could talk. We created a messaging system (empty files with specifc names). The creation of the file indicated a successful checkpoint indicating that the OS had finished writing everything. Existence of certain file names would indicate a message to the other app when it restarted. it wasn't elegant, but solved the problem before all of the later messaging and database technologies came about.
Could we do the same thing for Companionlink?
In our limitations, we were assured that only 1 app would be running at a time and that the apps would be automatically switched by an external environmental control so an app might not have finished what it was doing and so had to log progress.
Our approach was to find a common disk location where the two could talk. We created a messaging system (empty files with specifc names). The creation of the file indicated a successful checkpoint indicating that the OS had finished writing everything. Existence of certain file names would indicate a message to the other app when it restarted. it wasn't elegant, but solved the problem before all of the later messaging and database technologies came about.
Could we do the same thing for Companionlink?


Comment