Think about Loose Coupling | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Fair enough that SOAP doesn't really have anything to do with OO, however, and this is the bit that i'm really asking about...
When SOAP dispatches to my module and method, the first thing passed to that method is the name of module, which leads me to think that it is being called in an OO context, and so i should bless it once i get inside. That would then keep all the code within the module all OO. Am I missing something? I'm not talking about treating it like an object when I pass it back through SOAP, although that would work fine too, so where's the harm? In reply to Re^2: SOAP Modules (OO or not?)
by Cagao
|
|