Ok, finally had a chance to dig around in the Capability Map stuff in both jetspeed and the portal API areas.
I definately agree that the capability map direction is the one to go to add the features contained in my proposal. I have a few questions: 1) If I read the code right, no changes to either the Template or Profile Locators would be necessary if the directory structure continues to include media-type with no additional directories added to the heirarchy for browser. Am I missing anything? It looks like if the media-type is defined correctly based on user-agent -> media-type mapping it would just work. 2) Shouldn't the capability map be in the registry as a separate entity instead of a properties file or hardcoded? Or should those capability definitions be hardcoded/properties as Ralpael's previous message and the Portal API imply? I can imagine needing to define additional capabilities, so that would point to the former. 3) It looks like the current media-type registry is simply tied to content-type. This might imply that there needs to be a content-type registry, a capability registry, and the media-type registry would just tie these together. 4) What if a particular user wants to set her add or reduce her capability to something other than what her user agent maps to? Should this ability be included in the proposal? So the basic approach to implementation seems to be (contingent on the answers to the questions above): 1) Move the Capability Map into registry. 2) Add a content-type registry 3) Change the media-type entries to define a collection if content-type(1)/user-agent(*)/capability(*) instead. 4) Get the media-type set correctly in the rundata on login based on the user agent. 5) Test to verify that this maps correctly in psml, jslink and template realms. I would be more than happy to do this work and submit the patches for your approval, just want to make sure I'm going down the right path. I'll submit a more detailed, modified proposal once I have some of these questions more solidified. %regards -tk -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
