I'm not really sure what you are trying to get more then the question you linked.
The thing with a REST server is that you could start to understand it as a bunch of URLS (possibly with parameters) that do stuff.
Stuff is defined by either retreiving your data, inserting your records, etc etc. The parameters can be GET parameters or POST parameters, using the standards from the HTTP definition.
Using the service
What you do in the end is communication by HTTP. You request a resource from your REST service (for instance http:://yoursite.tld/user/id1, http://yoursite.tld/user?id=1, etc to get user 1) any way you would normally. Be it Curl, be it wget, be it java http object, just do a HTTP request. The same goes for changing that user (you could imagine using a POST here).
making the service
Just like a website you can make a service by creating anything that can parse these requests, and send back information. THe thing is, there is no central method / WSDL etc like in SOAP (both the strength and weakness of REST). Just make sure you can serve your data when a request is done, be it with a special file per request, a central index that redirects your requests, some .htaccess redirect trickery.
A simple method would be to use either a framework or some standard you yourself made. YOu can image your requests looking like /yourCommand/yourMode/yourData
where the first part tells your system what function / object / file to call, then the mode tells it what to do, and finally the data is what you need (for instance the ID of the user). You requests might look like /user/get/1
to retreive a user.