|
Re: PaceAppModified2 - was Re: Some feedback on current APP issues: msg#00576network.syndication.atom.protocol
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> |
|---|---|---|
| Previous by Date: | Re: PaceURINomenclature and PaceOnlyMemberURI: 00576, Elias Torres |
|---|---|
| Next by Date: | Re: PaceNoServiceDocument - Re: Some feedback on current APP issues: 00576, Sylvain Hellegouarch |
| Previous by Thread: | Re: PaceAppModified2 - was Re: Some feedback on current APP issuesi: 00576, Thomas Broyer |
| Next by Thread: | Re: PaceAppModified2 - was Re: Some feedback on current APP issues: 00576, Sylvain Hellegouarch |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |