Skip to:
AGL enhance use of "hat" high level API that hide and dispatch high-level abstractions to low-level implmentations.
That model is powerful if the high level is not bound to its low-level implementations, allowing many low level implementations.
So the high level apis must be able to use apis that are not described in their config.xml file.
That behavior must be protected using a platform permission.
Close for HH 8.0.3 release
I wonder if we should follow-up on that and define an
{#optional-binding}
<name = "foo">{/optional-binding}
And at least check the declared api names against what we dynamically request as we can otherwise pull in more or less anything, right ?
AGL enhance use of "hat" high level API that hide and dispatch high-level abstractions to low-level implmentations.
That model is powerful if the high level is not bound to its low-level implementations, allowing many low level implementations.
So the high level apis must be able to use apis that are not described in their config.xml file.
That behavior must be protected using a platform permission.