Skip to content

Purpose of the IOSDeviceLib's interface #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
zahhak opened this issue Dec 26, 2017 · 1 comment
Open

Purpose of the IOSDeviceLib's interface #30

zahhak opened this issue Dec 26, 2017 · 1 comment

Comments

@zahhak
Copy link

zahhak commented Dec 26, 2017

If we would like to state the following:

  • "The node code is there to be able to act as a proxy between the spawned process and the rest of the code"
    If this is true.. functions like upload,download, postNotifications should not be defined in the javascript code.

  • "The node code should serve as both proxy and api to be used from applications"
    If this is true... named functions are a nice idea.
    What seems wrong is the fact that currently the only ways to find what to pass in the uploadArray, downloadArray or postNotificationArray are to take a look at the mobile-cli-lib or go to the native code to see how we are parsing the array.

It seems the purpose of IOSDeviceLib's interface is not clear enough with the current implementation.
Please correct me if I don't understand correctly.

@Mitko-Kerezov
Copy link
Contributor

The purpose is the latter, namely:

The node code should serve as both proxy and api to be used from applications

I've added some docs in order to help clarify this matter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants