>First of all, why is this? Lets take for example, a VBScript that simple pops up a dialog box that tells you if there are UT replies waiting for you.
>
>You could simply do:
>
>oUT.GetReplies("username", "password")
>
>and do it all. Why make it any more complex than that? Why require 3 round trips to the server to do one thing?

For you, as I can see, you're mostly only using that method. Keep in mind that other people are using them all. We are already at about 17 methods and we will hit 100 in version 2 or 3. So, that's not the proper way to do it. Other methods are requiring several parameters. Those parameters belong to the method. Username and password do not belong to those. I'm not the only one saying that. You'll find a lot of articles that describe that methodology of avoiding passing the authentication as parameters as in every method.

>Also, would it be possible to send the username and password on every hit, but also allow for the header mechanism? That way, if you are using the header, or the cookie based, you can send blanks as the first two parameters? Otherwise, you can call the same method but pass the username and password, making it useable from any platform?

I wouldn't want to apply such a design and have to support it as well. Duplicating all methods in order to offer one version as is and one version with authentication is just not something I will support.