> To maintain loosely coupled Services, therefore, let's implement use case #1 > following the document style instead. In this situation, we build a Create > Employee Service after all, and it accepts an XML document as input, where > we don't really care what the document contains. Simply receiving the > document is sufficient to create the employee record; the header of that > document may contain other information like security-related content, but > its body need contain no parameters or other information.
... and the word "REST" is no where in sight. I can hear the "whooshing" sound going right over the Zapthink offices from here in Ottawa! Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca Coactus; Web-inspired integration strategies http://www.coactus.com
