On 8-Nov-2009, at 07:19, Brett Zamir wrote:
Yes, as far as I can tell, I agree it dosn't make sense to have different defaults per node, as querying that would be wasteful.
Requiring a node parameter in <default/> when node-specific defaults are required is an acceptable amount of waste, IMHO.
However, should we still add a "type" attribute or the like on <default/> to specify a default as to whether it was a collection or leaf node? For example, in PubSub Collection Nodes, pubsub#subscription_type and pubsub#subscription_depth might have their own defaults but only for collection nodes. Likewise might one wish to have leaf-node-only subscription defaults (e.g., Openfire's implementation has "x-pubsub#keywords" exclusively for leaf nodes subscription options).
What about pubsub#expire, which can be expected, in some instances, to have different defaults depending on node? I don't want to see a proliferation of attributes on the request, particularly when they can already be satisfied with one that already exists ("node").
-bjc
