Hi,

when I first started to play with WebServices I soon became disappointed about the lack of proper property-handling (property handling at all to be precise). Everyone I talked to said something like "There are no properties in WebServices as there are no states, stupid". That was neither new nor helpful to me. However looking closely into the subject, You will realize that there is no persistent object on server-side as well. It's just the illusion of an object. And that's what we need, the illusion of an object having methods and properties.

So I started to read... and found an article by Michel Fournier here in the UT RapoZine (December 2001) "Using SOAP header for authentication".

I knew this was the information I have been looking for when I read it, but it took me several months until I could start to play around.

I am now writing a WebService-class (a server and a client) that handles properties just like You are used to with "normal" objects (OK, no objects so far). It makes session-handling and authentification just a snap and allows to write methods that do not require 45 parameters.

My first trials really work like a charm and if I'm not overlooking something serious I might be ready to post the first version here in the download section within the next days/weeks (depending on Your demand and feedback).

Any response is gladly welcome.