[Chandler-dev] Some use cases and opinions

[Sam Halliday]

Hi,

On 5 Feb 2008, at 16:21, Randy Letness wrote:
>> The server doesn't support notifications at the moment so there  
>> really isn't a mechanism that would allow say a twitter or SMS  
>> notifications.  These would be great, and would get me using the  
>> server more.

When you say "server"... do you mean the actual server, or the webapp  
that is build on top of the server?

It seems to me that to accomplish my use cases, the server needs to  
support:-

- messaging/notification between users... but very limited. The users  
could not construct their own messages (it's not an instant messaging  
service), but it would allow for generated requests such as "add this  
event to your calendar" or "add this calendar to your account" and the  
responses.
- the ability to share tasks and events. It looks like the smallest  
sharable unit is a calendar (or collection as the webapp calls them).

Who is the best person on the dev team to speak to regarding  
implementing such features in the server? (not even exposing it to  
users at this point). Should I move these questions to the cosmo-dev  
list, or is it ok to ask here?

> There are a few protocols the server supports at the moment:
>
> - cmp(cosmo management protocol), used for account management
>  http://chandlerproject.org/Projects/CosmoManagementProtocol
> - morse code, used by Chandler to sync collections
>  http://chandlerproject.org/Projects/CosmoMorseCode
> - atom feed service/atompub, used by web ui
>  http://chandlerproject.org/Projects/CosmoFeedServiceSpec
> - webdav, webdav tickets, caldav
>  http://chandlerproject.org/Projects/CosmoWebdav
>  http://chandlerproject.org/Projects/CosmoTickets
>  http://chandlerproject.org/Projects/CosmoCaldav


Great... thanks!

-- 
Sam

http://fommil.me.uk
http://javablog.co.uk