> Dear all,
>
[quoted text clipped - 5 lines]
> in
> sop header rather that function parameter ?
Hi Serge,
IMHO is a design issue that you must resolve depending on your specific
requirements. Either way the basic goal is one - passing values. If you are
going to implement a small framework in your project and you can call your
web services from one central location may be it is better to use soap
headers. That way you will minimize method arguments, but it will be harder
to debug unless you provide some mechanism for this.
If you need to expose this web service for various devices and client may be
it is better to pass the value as an argument to each of your methods. Your
callers will be much happier :).
Still the decision is up to you.
Regards,

Signature
Martin Kulov
http://www.codeattest.com/blogs/martin
MCAD Charter Member
MCSD.NET Early Achiever
MCSD
serge calderara - 21 Feb 2006 08:19 GMT
hi, thnaks for your comment,
But then I could not see any difference then on passing parmater within soap
heder or public function to a web service. Sopa header is not even a big deal
to handle, to debug may be it is.
I am trying to find out a real guide lines information which could help.
In a similar way when you nee to select a communication protocol. Example
need fat reply means binary formater.
If anyone else have any ide thanks to post
regards
serge
> > Dear all,
> >
[quoted text clipped - 20 lines]
>
> Regards,