> ...I'd be vastly less concerned about seeing such > a component appear in a generic MyFaces PPR/AJAX library, when > we get around to that...
What about a slow start? Could be a tag namespace of: xmlns:tra="http://myfaces.apache.org/trinidad/ajax"; or xmlns:trp="http://myfaces.apache.org/trinidad/ppr"; then any components written that are not HTML in nature, but are simply PPR-AJAX related would be in this namespace. That way, if Trinidad's PPR functionality is extracted into its own library, these components could move with it to a new namespace? It provides a half-way point where there is functionality not specifically for Trinidad's HTML oriented components, and keeping them separate from the "core" components. This way there is a clear separation of functionality and goals?
