Yes these are very much limitations of web services. So would even
argue this is by You can't pass anything by reference, nor do they
support optional parameters.
returning a dataReader from a webservice is like
sending someone an oceanliner for valentines day.
It doesn't make any sense.
The philosophy of webservices is message-oriented integration. you need to
think in terms of sending and receiving discrete messages, not sending and
receiving objects such as datareader.
check this:
http://webservices.xml.com/pub/a/ws/2003/09/30/soa.html
re: "optional params are not supported"
True, if you are thinking in terms of VB calls.
But not true, if you are thinking in terms of extensible messages, with
optional pieces of those messages. In other words, the message itself is
not optional, but the contents of the message may vary. You can do this
with webservices.
-Dino
> Yes these are very much limitations of web services. So would even
> argue this is by You can't pass anything by reference, nor do they
> support optional parameters.