Re: [Ietf-caldav] Going from browser to application

[Julian Reschke <[e-mail]>]

Mike Shaver schrieb:
> On 5/16/06, Lisa Dusseault <[e-mail]> wrote:
>> When the same data can be viewed either as a Web page or as data to
>> be consumed by an application, there's a general issue over how to
>> get the user from one to the other.  Typically it's how you get the
>> user from browser to specialized application.
> 
> Content-disposition: attachment?
> 
> I'm not exactly sure why a browser can't be the thing that handles it
> correctly, but C-d:a is how servers are supposed to indicate "probably
> want the user to pick where this goes", by my recollection.

Yep, but I'm not sure how this helps here. Sending that header will 
cause user agents to display a download dialog. What we're looking for 
is something that triggers automatic invocation of a non-browser 
application for a specific URL.

> I don't like MIME type for this, since as you say it's the same data
> (in the same format), which seems to me to have the same undesirable
> characteristics as using a different scheme for data that comes over
> HTTP.

Depends on how you use the MIME type. The one I defined in 
<http://greenbytes.de/tech/webdav/draft-reschke-webdav-mount-04.html> is 
used to transport information about how to "mount" an HTTP URL in the 
system's WebDAV client. That information includes a base URL (mount 
target), a child collection to be displayed (which may be below the 
mount target), plus additional information (such as account).

Note sure how you would do that using response headers...

Best regards, Julian