I was wondering, what does it mean to write a client code which deals with resources whose state include links ?
Suppose we have a resource which can be addressed like this :
http://host:port/collection/1/2/3/4
We start from http://host:port/collection, then we get http://host:port/collection/1, etc, until we get http://host:port/collection/1/2/3/4.
What kind of client application we're writing here ? It seems that a code which deals with more than 2 levels (starting from http://host:port/collection/1/2) is actually a navigation tool which should allow a user to get back. Is it a reasonable characterization ?
Subscribe to:
Post Comments (Atom)
1 comment:
Interesting to know.
Post a Comment