On Fri, Feb 15, 2013 at 11:51 AM, John Carlson <[email protected]> wrote:
> I am against showing ids to the end user. With rest you can do a get on a
> collection uri and see all the entry ids.
>
A big aspect of REST architectural style is the ability to distribute
resource identifiers with other content, and to discover resources by this
means. But that doesn't imply the "end user" needs to see the identifiers.
Resource IDs can be associated with presentation data. For example, you
regularly GET pages that happen to include IDs of the form:
<a href="RESOURCE ID GOES HERE">HUMAN TEXT GOES HERE</a>
If you wanted, you could create a browser that doesn't show the resource
IDs. (Honestly, it wouldn't take much effort with all the open source
browsers available today.) The reason browsers expose resource IDs is
that's what the users wanted. Being "against showing ids to the end user"
is just your opinion. Not everyone agrees. I certainly don't. I favor a
world where users can usually look under the hood and satisfy their
curiosity about how things work.
_______________________________________________
fonc mailing list
[email protected]
http://vpri.org/mailman/listinfo/fonc
