-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 5/18/09 4:39 PM, Peter Saint-Andre wrote: > On 5/15/09 3:57 PM, Brian Cully wrote: >> In my world, subscription option defaults are better left relegated to a >> node, as nodes may then be able to calculate appropriate defaults based >> on their semantics, which may be different from node to node within a >> given pubsub service. > > That does seem more reasonable: you ping the node for default > subscription configuration options and you ping the service for default > node configuration options.
Sorry to take quite a while in response to this. While it is fine to be able to get node specific subscription defaults, I still think it would be nice to have a service-wide default (of lower priority than a node-specific one, of course): one for leaf nodes and another for collection nodes. Could an attribute "type" be added of value "leaf" or "collection" to be used when the "node" attribute is not used on <default/>?
My interest to see this is so that the client can work off of a general default in submitting subscription requests, saving the service's default so that the user can submit their options for new subscriptions without having to retrieve the node-specific options, but while still having an idea about the available options and being able to base their own preferences off of such a default.
Brett
