Re: How to return a user-defined data type object from a webservice?

"nano2k" <adrian.rotaru@xxxxxxxxxxx> wrote in message
news:761ec758-2131-4592-9f5a-1d457a8ec7e0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks John.
I understand and aggree entirely.
But my app is ment to work ONLY on .NET platforms. It is not a public
web site or smtg like that.
It's an "internal" application for a company that will use the app
inside its own VPN.
More than that, I'm being asked to secure the entire system so that
the webservice will only work with the designated client (also
developed by me).

So I find myself in this particular case, not in the general case. I
assure you I understand how interoperatibility works and its demands.

Anyway, your input was very good for me, but what do you say about my
particular situation? Creating standard XML schemas for each type I
want to "transport" would be a waiste of time, as I am 100% SURE my
webservice will only be accessible from a .NET client.

PS: I should have been more specific on this on my first post, my bad.
==========

If you're doing .NET to .NET, then you shouldn't be using Web Services - you
should be using .NET Remoting, or WCF with the NetDataContractSerializer.
These cover the case I mentioned, where it's important to be using the
correct version of the correct type. They both communicate the actual .NET
type name across the channel.

If, for some political reason you feel you must stick to ASMX web services,
then you can do something like have a translation layer than receives the
proxy type, then uses it to fill in an instance of the "real" type.
--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer


.

Relevant Pages
Loading