Re^3: SOAP Modules (OO or not?)

[ForgotPasswordAgain]

Since nobody else is saying anything, I'll just give my thoughts, which are as follows: WTF?!? You're instantiating an object of this class when calling some random method, like a method of the SOAP-exposed API? No, that's not good at all.

BTW, if you're looking for a role model distribution on how to do your classes, SOAP::Lite is not it at all. Wondered why its development ground to a halt, I don't think it's coincidental.

[Cagao]

Okay, a bit of background, I need a web service that 'internal' people will use, but could be developing their own front-ends.

So I thought, use SOAP, send me some valid XML and I'll do what you want, the Object will deal, for arguments sake, with customers details.

So someone can call the Customer service and send me new details to store in a DB, or alter an existing one, etc.

Hopefully I'll keep it as a nice object internally to make calling further subs nice and easy, and also call more external modules.

Any suggestions in this situation? I'll have around 10 such modules dealing with different things, and several methods for each one.