Skip to content

Access to proprietary APIs apart from HTML5 #656

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

Merged
merged 1 commit into from
Apr 15, 2016

Conversation

loxal
Copy link
Contributor

@loxal loxal commented Apr 14, 2016

No description provided.

@jfbastien
Copy link
Member

As written this isn't accurate: when embedded by a JavaScript engine then you only get access to JavaScript APIs, but in a non-JavaScript embedder you may be able to access any API the embedder decides to expose. Could you update to clarify?

@loxal
Copy link
Contributor Author

loxal commented Apr 14, 2016

This is great news, thanks for clarification!
@jfbastien I just pushed an update. If the wording is not appropriate, the gist of the question is fore sure. As this basically answers the question. “Can I develop native iOS apps compiling my — let’s say — COBOL code ;) to wasm and access iOS’ fingerprint API…”. Well, given that Apple will provide such a wasm VM version that provides access to those APIs.


## Will I be able to access proprietary platform APIs (e.g. Android / iOS)?

Yes but it will depend on the _environment where a wasm VM is embedded_. Inside a browser it is most likely that you'll get access to the same HTML5 and other browser-specific APIs which are also accessible through regular JavaScript. However, if a wasm VM is provided as an “app execution platform” by a specific vendor, it might provide access to proprietary platform-specific APIs of e.g. Android / iOS.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change "environment where a wasm VM is embedded" to "WebAssembly embedder". I think that's more consistent.

"most likely" isn't strong enough: you do get access to any existing web APIs, the same way JavaScript does.

I'd refer to NonWeb.md in the last sentence.

Also, Portability.md#api somewhere. I think this question is expanding on Portability.md#api.

@loxal
Copy link
Contributor Author

loxal commented Apr 15, 2016

I’ve just squashed a fix.

@jfbastien
Copy link
Member

Looks good, thanks!

@jfbastien jfbastien merged commit 2312afd into WebAssembly:master Apr 15, 2016
rossberg added a commit that referenced this pull request Apr 19, 2016
* Prettify section names

* Restructure encoding of function signatures

* Revert "[Binary 11] Update the version number to 0xB."

* Leave index space for growing the number of base types

* Comments addressed

* clarify how export/import names convert to JS strings (#569) (#573)

* When embedded in the web, clarify how export/import names convert to JS strings (#569)

* Fixes suggested by @jf

* Address more feedback

Added a link to http://monsur.hossa.in/2012/07/20/utf-8-in-javascript.html.  Simplified the decoding algorithm thanks to Luke's feedback.

* Access to proprietary APIs apart from HTML5 (#656)

* comments
lukewagner pushed a commit that referenced this pull request Apr 28, 2016
* Prettify section names

* Restructure encoding of function signatures

* Revert "[Binary 11] Update the version number to 0xB."

* Leave index space for growing the number of base types

* Comments addressed

* clarify how export/import names convert to JS strings (#569) (#573)

* When embedded in the web, clarify how export/import names convert to JS strings (#569)

* Fixes suggested by @jf

* Address more feedback

Added a link to http://monsur.hossa.in/2012/07/20/utf-8-in-javascript.html.  Simplified the decoding algorithm thanks to Luke's feedback.

* Access to proprietary APIs apart from HTML5 (#656)

* comments
lukewagner added a commit that referenced this pull request Apr 29, 2016
* Merge pull request #648 from WebAssembly/current_memory

Add current_memory operator

* Reorder section size field (#639)

* Prettify section names (#638)

* Extensible encoding of function signatures (#640)

* Prettify section names

* Restructure encoding of function signatures

* Revert "[Binary 11] Update the version number to 0xB."

* Leave index space for growing the number of base types

* Comments addressed

* clarify how export/import names convert to JS strings (#569) (#573)

* When embedded in the web, clarify how export/import names convert to JS strings (#569)

* Fixes suggested by @jf

* Address more feedback

Added a link to http://monsur.hossa.in/2012/07/20/utf-8-in-javascript.html.  Simplified the decoding algorithm thanks to Luke's feedback.

* Access to proprietary APIs apart from HTML5 (#656)

* comments

* Merge pull request #641 from WebAssembly/postorder_opcodes

Postorder opcodes

* fix some text that seems to be in the wrong order (#670)

* Clarify that br_table has a branch argument (#664)

* Add explicit argument counts (#672)

* Add explicit arities

* Rename

* Replace uint8 with varint7 in form field (#662)

This needs to be variable-length.
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

Successfully merging this pull request may close these issues.

2 participants