Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • While I agree entirely with what you are saying, I think you might have misunderstood the description (or I did :)). The calendarid is a back-end implementation detail where it is the same for every user. If I did misunderstand, then you are correct, as I explained in my above answer :) Commented Mar 10, 2012 at 16:30
  • Got it. It wasn't clear that only one calendar was used on the backend from the question. If its an application wide setting, then you certainly don't want it to be changed by the end user (that'd be analogous to letting the end user select the db name as part of the URI), so yeah option two is the way to go. Good catch. Commented Mar 10, 2012 at 16:41
  • Yeah, sorry. It's an app for our publics, and it shows a single calendar to everyone. I should have explained that better. Commented Mar 10, 2012 at 16:47