however, i like this direction. what about allowing the client to
specify arbitrary preference kvp's (key-value pairs) in the signup
request? the server wouldn't have to interpret their semantics, just
store them as prefs. then, when the account is activated, we can check
for the specific pref that says "subscribe to collection x" and do
that.
+1
Also, I'm for keeping the logic of checking for and interpreting
preferences on the client side, which would mean putting the "add
subscription based on a preference" logic in the JavaScript. I don't
really like the idea of building logic to interpret preferences into
the server, but I'm definitely interested in hearing other thoughts
on this.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
