Enable iCal to subscribe to CalDAV collections

On 4/6/06, bug-commentosafoundation.org <bug-commentosafoundation.org> wrote:
> http://bugzilla.osafoundation.org/show_bug.cgi?id=5596
>
>
>
>
>
> ------- Comment #1 from townsosafoundation.org 
2006-04-06 11:58 PST -------
> Right now, we support a possible work around. If you do
a GET on a collection,
> it will return the iCalendar data for the entire
collection. This isn't part of
> the CalDAV standard, but it will work. That might help
Ted in the short term.

it's not a workaround; it's a feature!

> But, I think the idea of a virtual resource that allows
a GET to a canned
> report would be interesting.

i don't. it's an awkward hack. i'd rather see caldav
specify that a
GET on a calendar collection optionally return an icalendar
object
containing all of the components in the collection. which is
exactly
what cosmo does right now.
_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

I'm not sure whether we are talking features or bugs here,
but the  
backdrop is this:

Julie and I used to share our calendars via a private behind
the  
firewall WebDAV server.  I would like to use cosmo-demo, as
a  
prototype of a hosted service, to replace that usage.   I
have bunch  
of calendars that I've shared up to cosmo-demo.   Now my
replacement  
laptop is finally here, and I want to use today's iCal, not
some  
future CalDAV compliant version, to subscribe (read only) to
some of  
those calendars.

The big question is: Is there a way to do this or should I
resurrect  
the WebDAV server and take those calendars off of
cosmo-demo?

Ted


On Apr 6, 2006, at 1:39 PM, Brian Moseley wrote:

> On 4/6/06, bug-commentosafoundation.org <bug- 
> commentosafoundation.org> wrote:
>> http://bugzilla.osafoundation.org/show_bug.cgi?id=5596
>>
>>
>>
>>
>>
>> ------- Comment #1 from townsosafoundation.org 
2006-04-06 11:58  
>> PST -------
>> Right now, we support a possible work around. If
you do a GET on a  
>> collection,
>> it will return the iCalendar data for the entire
collection. This  
>> isn't part of
>> the CalDAV standard, but it will work. That might
help Ted in the  
>> short term.
>
> it's not a workaround; it's a feature!
>
>> But, I think the idea of a virtual resource that
allows a GET to a  
>> canned
>> report would be interesting.
>
> i don't. it's an awkward hack. i'd rather see caldav
specify that a
> GET on a calendar collection optionally return an
icalendar object
> containing all of the components in the collection.
which is exactly
> what cosmo does right now.
> _______________________________________________
> cosmo-dev mailing list
> cosmo-devlists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev




_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

On 4/6/06, Ted Leung <twlosafoundation.org>
wrote:

> The big question is: Is there a way to do this or
should I resurrect
> the WebDAV server and take those calendars off of
cosmo-demo?

yes - subscribe to the url of the calendar collection.

<http://wiki.osafoundation.org/bin/view/Docu
mentation/CosmoEndUser>

what you cannot do is use ical to subscribe to, then edit
and
republish, a calendar that julie originally published, and
vice versa.
with ical, you can either publish a calendar or subscribe to
it - not
both.
_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

On Apr 6, 2006, at 3:39 PM, Brian Moseley wrote:

> On 4/6/06, Ted Leung <twlosafoundation.org>
wrote:
>
>> The big question is: Is there a way to do this or
should I resurrect
>> the WebDAV server and take those calendars off of
cosmo-demo?
>
> yes - subscribe to the url of the calendar collection.
>
> <http://wiki.osafoundation.org/bin/view/Docu
mentation/CosmoEndUser>

calendar url: <
http://cosmo-demo.osafoundation.org/home/Work-2/>
I was prompted for auth, which i supplied,

but I got:

Error message: Access is denied at http://cosmo- 
demo.osafoundation.org/home/Work-2/ with this login and
password.

>
> what you cannot do is use ical to subscribe to, then
edit and
> republish, a calendar that julie originally published,
and vice versa.
> with ical, you can either publish a calendar or
subscribe to it - not
> both.

One way read only would be fine.

----
Ted Leung                 Open Source Applications
Foundation (OSAF)



_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

Hello,

Brian Moseley wrote:
>>But, I think the idea of a virtual resource that
allows a GET to a canned
>>report would be interesting.
> 
> 
> i don't. it's an awkward hack. i'd rather see caldav
specify that a
> GET on a calendar collection optionally return an
icalendar object
> containing all of the components in the collection.
which is exactly
> what cosmo does right now.

This feature breaks plain HTTP browsing btw 
Not a big deal, but might be helpful to to
some.

Would you consider making that an option?
Because that GET may become very expensive on
large calendars.  I am worried about lazy
CalDAV clients and non-CalDAV-aware HTTP and
WebDAV browsers/spiders ( who would pull the
entire collection either by accident or instead
of the components they actually need ).

Could there be an option to forbid this?

Best regards,
Kervin

_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

On 4/6/06, Kervin L. Pierre <kervinadevsoft.com> wrote:

> This feature breaks plain HTTP browsing btw 

in the vanilla http sense, yes, but webdav says that the
response to
GET for a collection is undefined, so we can really do
whatever we
want here, and i think ical interop is more important.

since cosmo has a builtin repository browsing web ui, and
since you
can easily browse the calendar collection with PROPFIND,
i'm not too
worried about http browsing.

and yet, there is a bug in bugzilla to check the Accept
request header
to see if the client would prefer to GET the resource as
text/html
rather than text/calendar. i can' t promise anybody will
get around to
implementing it, but you never know.

assuming ical somebody gains caldav support, i won't have
any problem
changing the behavior to the "expected"
text/html response.
_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

On 4/6/06, Ted Leung <twlosafoundation.org>
wrote:

> calendar url: <
http://cosmo-demo.osafoundation.org/home/Work-2/>
> I was prompted for auth, which i supplied,
>
> but I got:
>
> Error message: Access is denied at http://cosmo-
> demo.osafoundation.org/home/Work-2/ with this login and
password.

i doubt your username is Work-2  try again
with /home/twl/Work-2/ or whatever.
_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev

Yeesh.  Chalk me up for major points on pilot error.

That did it.

On Apr 6, 2006, at 5:14 PM, Brian Moseley wrote:

> On 4/6/06, Ted Leung <twlosafoundation.org>
wrote:
>
>> calendar url: <
http://cosmo-demo.osafoundation.org/home/Work-2/>
>> I was prompted for auth, which i supplied,
>>
>> but I got:
>>
>> Error message: Access is denied at http://cosmo-
>> demo.osafoundation.org/home/Work-2/ with this login
and password.
>
> i doubt your username is Work-2  try again
with /home/twl/Work-2/  
> or whatever.
> _______________________________________________


_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev