-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 9/14/09 4:06 PM, William Edney wrote: > Peter (and all) - > > Since you asked... :-). > > One thing I struggled with a bit is the ability to configure node > options for a server when auto-creating nodes. > > For instance, I wanted to be able to configure nodes to have > pubsub#publish-options such that all auto-created nodes would have an > access model of 'open'. > > So what I really wanted to do was configure the server to say 'all nodes > auto-created from now on should have these options until I say > differently'.
This sounds like a server option about setting the default node config, not something that we'd need to document in the spec. > Obviously, you'd want to limit this in some way, but my thought here was > that collection nodes could come in handy. If I'm the node owner of a > collection node, then I could ask the server to configure nodes that get > auto-created 'in my collection' in a particular way. Aha, I see. Hmm. One problem is that a node that's part of your collection might also be part of someone else's collection. How does the pubsub service decide which collection's configuration is operative? Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqxbBYACgkQNL8k5A2w/vzVQwCgwmXwOzKEB/8YkOuqZ2b/F+je 0/YAoMoEAUlkHHXi5UKjkkry3rOc4yDz =NbZA -----END PGP SIGNATURE-----
