Sean Landis wrote:
The nature of the data is
a clientId and a callId. These are going to be used for governance and
should be part of every call in our environment. It seemed to me that
since it was not application related, that it ought to be hidden. I'd love
to hear about alternatives
Based on what you wrote Adam, it sounds like you would agree that using
hidden parameters in this case doesn't break REST. Now that I've explained
what we are trying to accomplish, can you suggest a more RESTful
approach? We are very interested in being as RESTful as possible.
Sounds like
2 matches
Mail list logo
