Architecture Open Issues

Strawman picture: CalendarArchitectureDiagrams

Discovery

• Q: How do I find another Chandler user's repository?
  • A: There's a central server.
• Q: Details?

Notification

• Q: If one client makes a change to a calendar on a repository, how do the other clients who are viewing this repository find out about it?
• Q: How does this work with information in other types of repositories? (CAP, IMAP, LDAP)
• Q: How does this work for other types of clients to a RAP repository? (CAP, IMAP, LDAP)

Composite items, composite views, aggregation

My client can see what looks like a set of events in a calendar. Some of the information comes from a CAP server (work meetings, work schedule), some of the information comes from my local repository (my personal calendar, related contact information), some of the information comes from an LDAP server (other contact information).

• Q: When I make a change, how do we know which repositories to write back to? Do we have meta information for each item? For each attribute?
• Q: Can I do one query across all of the repositories, with the same query language?
• Q: Is the client aware that the data comes from multiple repositories? Is the user aware?
  • A: I assume the answer is yes.
• Q: Do we write adaptors for LDAP, CAP, IMAP, so that they all look like RAP?
• Q: When I do a read, is the information aggregated in a middleware layer? Is it aggregated in the client?
• Q: If I were to write a web client, and wanted the "aggregated" items, does the code I write talk to RAP? Does the code I write link to some middleware layer, that does both aggregation and RAP?
• Q: If RAP is not the API to this "middleware" layer, what is the API?

RAP

• Q: What is the query language?

Scheduling (meeting invitations, etc)

Proposal: iTIP style meeting invitations, etc. over RAP for Canoga. When I invite you to a meeting, I place an "invitation" item in your repository. Your client "notices" this new invitation in your repository and responds to that "invitation" however it wants: a special view of "invitations", an email message, a system tray notification, a pop up dialog, etc.

• Q: Any significant problems with this strategy for the architecture?

-- KatieCappsParlante - 03 Apr 2003