>Thanks. Again, from a technical perspective, what is the advantage of making use of the SOAP header as you do?

When you use the Universal Thread Web site, do you login for each transaction? Probably not, it's the same approach we use for the Web Service. Those two environments are stateless. Thus, they require a mecanism to authenticate the user for each transaction. The Universal Thread Web site uses a cookie. The Web Service uses the SOAP header. Basically, it's about the same technique.

If we would have only one or two methods, then, we wouldn't bother and have the requiremets to pass those two parameters for each transaction. But, we have a lot and we'll have much more. So, you don't want to have to pass username and password for each transaction. This is why it's done like that.

Also, the mecanism in place takes care of all validation messages as well. So, if you would use the Intellisense approach and just fire a method which would generate a validation message, that approach wouldn't work as you'll end up with an error. Our mecanism takes care of that. For example, if you want to search for a forum that doesn't exist. We have to return a message.