Re: PaceContentNegotiationSection

In my setup, the client (my client imp.) makes a secondary request at http://
example.com/ shifting the q-value for 'application/atomserv+xml' to "1", the 
server responds to such requests with the introspection document, everything 
is automated.

Really, I thought this was the purpose of the MIME type, under the examples 
others have given there's no reason I can fathom that it can't be an 
existing XML MIME type of some sort, 'applicaton/xml' or such.  The only 
reason I could deduce for it was to allow negotiation.

-EJB

>-----Original Message-----
>From: James M Snell [mailto:jasnell-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx]
>Sent: Friday, August 18, 2006 04:03 PM
>To: eric-MkmoNbc1SAncr/OS1auqaA@xxxxxxxxxxxxxxxx
>Cc: 'Thomas Broyer', atom-protocol-O6w3ZxSwtmQ@xxxxxxxxxxxxxxxx
>Subject: Re: PaceContentNegotiationSection
>
>
>
>Eric J. Bowman wrote:
>> It seems to me that the purpose of an "introspection" document is to allow a 
>> first-time visitor to a domain to determine what compatible services are 
>> available.  The debate about the service document is concerned with being 
>> able to find collections automatically, so why is finding the service 
>> document a manual operation?
>> 
>
>It doesn't have to be.  APP leaves it undefined.  In one of our
>implementations, we're using a <link rel="introspection" href="..." />
>to find it. Other approaches are possible, results may vary.
>
>> [snip]
>> Under my setup, the service document is accessed once in a conneg scenario, 
>> after which the user has their own service document (userid.atomsrv) cached 
>> on their client, and when it needs refreshing it may just be requested, 
>> instead of being renegotiated.
>> 
>
>In your setup, how does the client initially discover the URL used to
>access the service document?
>
>- James
>