Nov 03, 2013 12:49 PM|dotnetterAMG123|LINK
Hello, the request/response design pattern is pretty standard in the implementation of modern enterprise and commercial web services. Essentially, the parameters sent to the service are properties of a parent request object, like MyServiceRequest,
and the data and information returned from the service are properties of a parent response object, like MyServiceResponse.
So, is there a simple, standard, way to describe a web service, that does *not* use the request/response design pattern? For example, a web service that accepts 3 different parameters, and returns a generic list of objects? I would say this example
uses simple types instead of a request/response design pattern. Is there a more appropriate, general technical term to describe this type of web service that does *not* implement a request/response design pattern?