Re: [apps-discuss] Fwd: Media type for lists of changed URIs?

[Jan Algermissen <[e-mail]>]

On 08.01.2014, at 16:29, Darrel Miller <[e-mail]> wrote:

> Jan,
> 
> I'm sure you could shoehorn it into a bigger media type like atom or

Yeah ... that's the big solution[1] (and [2] for the cooler kids), including maybe delta-updates. Wanted the less-overhead solution first.

> activity stream, but I haven't seen anything that fits that specific
> need.  I'm not sure I follow your prev-archive scenario.  Do you want
> a user to be able to ask, "what were the last-updated-dates on these
> resources, yesterday, and the day before, etc"?

I want to avoid the situation where the client needs to understand the URI structure of the 'update-event' pages, e.g.

/items/changes/2013/01/01/01
/items/changes/2013/01/01/...
/items/changes/2013/01/01/24
/items/changes/2013/02/01/01
/items/changes/2013/02/01/...
/items/changes/2013/02/01/24

Because then I need more spec-parts (URI template vars, for example).

Instead, the client could start with a /changes/current (uncacheable) page and then proceed back in time through archived (cacheable) pages.

Jan


Credit where credit belongs:
[1] http://www.infoq.com/presentations/robinson-restful-enterprise
[2] http://roy.gbiv.com/untangled/2008/paper-tigers-and-hidden-dragons

> Darrel
> 
>> 
>>> On Jan 8, 2014 9:46 AM, "Jan Algermissen" <[e-mail]>
>>> wrote:
>>> Hi all,
>>> 
>>> I am about to work on a media type for transferring lists of URIs of
>>> resource that have changed to an 'observer' of a collection of resources.
>>> 
>>> It just occurred to me that something like that might already exist in the
>>> context of cache invalidation protocols.?
>>> 
>>> Jan
>>> 
>>> 
>>> _______________________________________________
>>> apps-discuss mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>> 
> _______________________________________________
> apps-discuss mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/apps-discuss