Site-Specific Preferences: Difference between revisions

Jump to navigation Jump to search
m
Line 226: Line 226:
<strong>Should we use the contract ID as the arbitrary identifier for the grouper, and how do we retrieve that from an instance of the component?</strong>
<strong>Should we use the contract ID as the arbitrary identifier for the grouper, and how do we retrieve that from an instance of the component?</strong>


The <var>group<var> method extracts and returns the site to which the given site belongs.
The <var>group</var> method extracts and returns the site to which the given site belongs.


Groupers are independent of the service to permit extensibility (overriding of the default grouper, registration of alternative groupers for specific URIs/prefs, etc.), although there is little extensibility in the current architecture, and it's not entirely clear what kinds of extensibility will prove useful.
Groupers are independent of the service to permit extensibility (overriding of the default grouper, registration of alternative groupers for specific URIs/prefs, etc.), although there is little extensibility in the current architecture, and it's not entirely clear what kinds of extensibility will prove useful.
canmove, Confirmed users
2,056

edits

Navigation menu