On 7/13/06, Katie Capps Parlante <[EMAIL PROTECTED]> wrote:
Sheila Mooney wrote:
> + Emailing items to a collection on Cosmo ie: Send a /Event to
> [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
i assume that we're not talking about email-based event scheduling yet?
- The ".osaf" service needs to be able to receive email. Something needs
to process that email and create events that land in cosmo.
i think this is best handled as an email server plugin or extension
that can talk atom or caldav to cosmo. the alternative is for cosmo
itself to accept smtp, which is possible but probably not wise :)
Questions:
- How does error handling work? What if Andi sends "/Evt pto thurrsday"?
a bounce message?
- How expensive is this to implement on the service side?
probably not terribly so, since we probably won't have to handle high
volumes of such traffic.
- Is this a cosmo feature or a service feature?
could be either. i can imagine shipping plugins for a few popular mail
servers that do this, or at least one, with a documented api for the
nlp and server communication. i can also imagine doing it in a much
more ad hoc fashion just for .osaf and perhaps simply sharing some
info about our experience on the wiki.
> + RSS in and RSS out via desktop/web access
Examples?
yeah, i'm having trouble imagining what you might be thinking of.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
