logo       

Re: PaceAppModified2 - was Re: Some feedback on current APP issues: msg#00576

network.syndication.atom.protocol

Subject: Re: PaceAppModified2 - was Re: Some feedback on current APP issues


When you insist that the rel='edit' and rel='self' MUST be the same, then it
is not possible for me to maintain one representation with thr:updated and
thr:count, and another one without.

By treating the Atom ID as an XML ID you require back-end changes to be
reflected on the front end, and this is my problem here. I am not
misinterpreting anything.

-EJB

>-----Original Message-----
>From: Thomas Broyer [mailto:t.broyer-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx]
>Sent: Friday, August 18, 2006 07:16 AM
>To: 'Atom-Protocol'
>Subject: Re: PaceAppModified2 - was Re: Some feedback on current APP issues
>
>
>2006/8/16, Eric J. Bowman:
>>
>> Under either app:modified Pace, a change to thr:count or anything else in the
>> resource, but not the representation, requires a change to app:modified.
>
>So you misinterpreted.
>
>PaceOrderCollectionsByAppModified does not require such a thing.
>
>> Since app:modified faces the client, and has been changed, the MD5 value of
>> that <entry> document has been changed even though it hasn't been <updated>.
>
>app:modified might only face the client in the collection feed and be
>excluded from the standalone entry representation (where it's not
>needed).
>
>--
>Thomas Broyer
>
>





<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise