There is a discussion as to whether the ALTO client needs to interpret HTTP status codes. I've started this thread to discuss that.
Here's my view: We now have a REST-ful protocol and made a conscious decision to go this way. REST-ful protocols are built upon making requests and following links to other resources. (This is why we restructured the existing protocol to remove all references to "ALTO Request" and "ALTO Response".) Therefore, the ALTO protocol is *not* a traditional client-server protocol like TCP, but is instead an encoding for HTTP resources that allow clients to discover the type of information described in the initial problem statement. Replicating HTTP status codes to the ALTO layer sounds like we are replicating a lot of what HTTP does already. I understand that someone using ALTO should not be burdened with HTTP status codes. My difference in opinion is that I think that should be an implementation detail hidden behind the API an ALTO Client exposes. Thanks, Rich
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
