Hello,
Any idea what happens, when /dav/calendars is returned in calendar-home-set?
To answer my own question:
This returns a lot of output:
curl -XPROPFIND -u myself:password -H'Depth: infinity'
-H"Content-Type: application/xml; charset='utf-8'" --data "
"
Hello,
Any idea what happens, when /dav/calendars is returned in calendar-home-set?
To answer my own question:
This returns a lot of output:
curl -XPROPFIND -u myself:password -H'Depth: infinity'
-H"Content-Type: application/xml; charset='utf-8'" --data "
"
Hello,
what is the status of this? Are the theoretical concerns clarified by
now?
About CALDAV:calendar-home-set:
While after logging in a user is supposed to find the list of the owned
calendars available with CALDAV:calendar-home-set, the specification
says this is an URL and the calendars
dio buttons for access type
(read|write)), so its owner could share his/her calendars/contacts
directly from the existing GUI.
Please let me know if I can provide additional details.
Thanks,
Anatoli
*From:* Ken Murchison
*Sent:* Friday, May 25, 2018 10:29
*To:* Cyrus Devel
*Subject:* Re: sh
radio buttons for access type (read|write)), so
its owner could share his/her calendars/contacts directly from the
existing GUI.
Please let me know if I can provide additional details.
Thanks,
Anatoli
*From:* Ken Murchison
*Sent:* Friday, May 25, 2018 10:29
*To:* Cyrus Devel
-imapd/issues/2373, so it's not lost
in the mails archive.
Please let us know if the community can sponsor the development.
Thanks,
Anatoli
*From:* Anatoli
*Sent:* Monday, April 09, 2018 00:40
*To:* Cyrus Devel
*Subject:* Re: shared xDAV resources
Bron, Ken,
Thanks for your explanations.
Do you
Devel
*Subject:* Re: shared xDAV resources
Bron, Ken,
Thanks for your explanations.
Do you consider this is something possible to implement for an outside
developer, i.e. without Cyrus HTTP/DB implementation internals
understanding, nor solid knowledge of xDAV RFCs? I'd like to
collaborate
:* Saturday, April 07, 2018 21:53
*To:* Bron Gondwana, Cyrus Devel
*Cc:* Ken Murchison
*Subject:* Re: shared xDAV resources
I originally wrote the code to handle public calendars in the "shared"
namespace, but I focused on user calendars first, and public calendar
support got tossed on
l 07, 2018 21:53
*To:* Bron Gondwana, Cyrus Devel
*Cc:* Ken Murchison
*Subject:* Re: shared xDAV resources
I originally wrote the code to handle public calendars in the "shared"
namespace, but I focused on user calendars first, and public calendar
support got tossed on the back burner. I
Yes, these are related items.
On 04/08/2018 10:08 PM, ellie timoney wrote:
Is this thread covering the same ground as
https://github.com/cyrusimap/cyrus-imapd/pull/2307 ? I don't know DAV
well enough to tell.
On Sun, Apr 8, 2018, at 10:53 AM, Ken Murchison wrote:
I originally wrote the
Is this thread covering the same ground as
https://github.com/cyrusimap/cyrus-imapd/pull/2307 ? I don't know DAV
well enough to tell.
On Sun, Apr 8, 2018, at 10:53 AM, Ken Murchison wrote:
> I originally wrote the code to handle public calendars in the "shared"
> namespace, but I focused on user
Ken knows this code best. I bet there's something which is requiring
that there's a user on the mboxname because we implement the same
behaviour at FastMail by having a separate user on which shared
resources are kept. The DAV resources are stored per-user, and
without a place to keep them for
Hi All,
I'm trying to understand the code responsible for enumerating user
calendars (and xDAV resources in general) to try to make the discovery
work for shared resources too (currently there's no way to access shared
resources with Apple xDAV client implementation, yes with Thunderbird as
13 matches
Mail list logo
