You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a deployment scenario where the AM and (singular) host are tightly coupled and there's no possibility of the AM needing to connect with outside hosts, does it make sense to build in optionality around the host/AM communication? Do we want these to count as "UMA-conforming", or just "UMA-like" if incomplete?
The text was updated successfully, but these errors were encountered:
Note that if we separate out "phase 1" (introduction) into its own generic module, we could pull this module into UMA by reference, potentially giving it an optional conformance switch. That would accomplish the goal above.
In a deployment scenario where the AM and (singular) host are tightly coupled and there's no possibility of the AM needing to connect with outside hosts, does it make sense to build in optionality around the host/AM communication? Do we want these to count as "UMA-conforming", or just "UMA-like" if incomplete?
The text was updated successfully, but these errors were encountered: