Skip to content
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

Explicitly enable colocated AMs/hosts? #67

Closed
xmlgrrl opened this issue Aug 29, 2012 · 3 comments
Closed

Explicitly enable colocated AMs/hosts? #67

xmlgrrl opened this issue Aug 29, 2012 · 3 comments
Labels
core Related to (original UMA1) core spec scope; may use obsolete language

Comments

@xmlgrrl
Copy link

xmlgrrl commented Aug 29, 2012

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?

@xmlgrrl
Copy link
Author

xmlgrrl commented Dec 9, 2012

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.

@xmlgrrl
Copy link
Author

xmlgrrl commented Dec 21, 2012

There's now a generic module for this, but currently it's pulled into UMA core on a required basis.

@xmlgrrl
Copy link
Author

xmlgrrl commented Jun 25, 2014

This is now handled by the "API extensibility profiles".

@xmlgrrl xmlgrrl closed this as completed Jun 25, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Related to (original UMA1) core spec scope; may use obsolete language
Projects
None yet
Development

No branches or pull requests

1 participant