Re: Bookmark 'stability'

On Fri, Sep 28, 2012 at 9:14 AM, Steve Klabnik <[email protected]> wrote:
>> Some interactions which are simply repeatable. Ie, I go to bookstore api,
>> pick the most popular book today and bookmark it. The every day the app
>> checks and record its popularity so that I can see the trend over time. If
>> that bookmark stops working the app is pretty much screwed.
>
> Sounds like someone should have written the app better.

Really? (Talk about trolling.) How would you deal with the situation
where a uri is acquired from search results? Search results change
fairly often if you use modern search technologies like lucene, etc
and are certainly not guaranteed to stay the same if new items are
added that match the query. How should we procede when the client is
given a url by a user or a third component of the (distributed)
system? Surely we don't want to implement existing capabilities just
so that we have all the information to refollow a hypermedia trail.
The whole point of this exercise is to leverage the work and data of
existing system.

>> There many more situations like this once you get into building real
>> applications.
>
> Nice troll. Well, I'm done here.

It wasn't meant as a troll, i was merely pointing out that the two
example i gave are not the only ones i have encountered.

Peter
barelyenough.org