Web Service with complex paramters and return types

[J.Marsch]

I'm starting to think about my first web service.

In order to do its job, this web service needs to have a lot of inputs, and
it needs to return a batch of records.

I don't want the service to be "chatty". If I were doing remoting, I'd
create a marshal by value class to contain the input parameters, and another
to return the results.

What do I need to do if I want my web service to accept/return complex data?
Declare an interface and use that as the input param (and another for the
output)? something else?

This web service must be compatible with non-.Net clients, so I don't want
to do anything that is proprietary to .Net.

 

[MSFT]

Hello,

I think you may consider a XML string as the input parameter of web
service, it can be consume by a .NET web service, and also can be post by a
non-.Net clients. In .Net web service, you can easily convert this string
to a XMLDocument object, even convert to a custom component.

Luke
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)