Radovan Janecek wrote:
> I'm using RSS+HTTP as an example of coarse grained interface since I started
> blogging. A blog could have fine grained interface like: getLastPost,
> getPrevious, getNext, getAllSince, etc. Instead, you do one GET, you've got
> many items in the feed, and then you can do whatever you want with them. If
> there was getNext and similar, the subsequent calls would have to know about
> each other and bare some contextual information (or even be part of some
> distributed transactions...).
I think there is room for a design which returns iteration indexes on the
initial call so that traversal would work.
However, I continue to wonder why everyone just can't seem to get the idea of
mobile code. When you have mobile code in a situation like this, you can put
the iteration context either local or remote and you can update the iteration
independent of the clients use of the interation index. The ability to avoid
remote round trips then becomes a dynamic optimization that you can modify
dynamically as well as optimize historically.
It's really entertaining to set back and watch various attempts to completely
reinvent or at least try to reinvent technologies which already exist and are
so
capable of solving these problems directly and completely with no compromize
necessary.
Gregg Wonderly
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
