• Where to include authentication information? (parameter in service call, well defined location that service call knows to look)
• Where to store auth/z information? (for ticketed/owned/subscribed)

Option 1:

• Make users pass information to service call each time (current model, super-anemic)

Option 2:

• Initialize "Service" object with necessary credentials. Multiple service objects floating around, possibly 1 per Collection (calendar) object?

Option 3:

• Make Collection (calendar) objects second class objects - put service calls here.

-- TravisVachon - 26 Feb 2007