> I think the best thing to do would be to have a standalone calendar
> backend, communicating with James as transport,
As a James commiter I can see this as being a sensible route, James exposes
the Mailet API which would provide hooks into the mail system for icalendar,
or indeed any other ma
Jeff Prickett wrote:
>Scott Sanders wrote:
>
>>Calendar is much more apropos in JAMES IMHO. I think that JAMES could
>>become an Exchange killer :)
>>
>
>Good point, I would accept that place as a home for the back end
>objects. Possibly split
>iCalendar between JAMES and Jetspeed or make it its
