If you hit the above url using your browser or using a java based client or using Postman, result will always be the User XML whose Id is 1 because the server does not store any information about the client.
The restful service implementation that handles this request does not need to remember or know about any previous interaction with the client invoking the service.
All the information it needs to serve or process the request is provided and available in the request itself. It needs the user id, which it gets from the request URL itself and it is 1, it fetches the user details and returns the XML response.
For stateless services, if you need to change the response you would need to change the request details or the context values you pass in the request (so in addition to the URL it could also be the HTTP request headers like content type or Accepts, etc)
State: One of the good example of maintaining state of request is say JSP where session is created and you can store values in it. You will get to know that state is maintained say login when user visits the page. Next request server in this case will be using data stored in session or token stored in session for authentication or authorization.
Statelessness: No session of any other means is there to record whether request is first request or second. All rest services are Statelessness services and if you hit it multiple times it will treated as new request. You cannot have session kind of concept here. All responses from service will be send based on request not on any stored data as it is not there.
Eliminate 95% of the weeds in your lawn by mowing 3 inches or higher. Then plant tiny ads:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop