Basically, yes. The real object lives on the server and its
code is executed there. You get a handle (sometimes called
a proxy object since it stands in as the proxy for the real,
remote instance) on the client side
that takes care of marshalling the arguments (rolling them up
into the XML wire format) and getting them sent to the server
where the actual method runs. Any return value is again marshalled
back into XML and returned to the caller, which turns things
back into perl values.
| [reply] |
Actually, I'm not sure that's true. I don't believe the object really exists on the server side. When I call methods on my local object, it looks like SOAP::Lite is sending the state of the object via XML each time, and the server then bless's that object, and calls the method on it.
Also, you can run a SOAP::Lite server via a simple CGI transport. If you are running CGI with Apache, those "servers" are all running in different processes. How could it maintain a persistent object across multiple processes?
-Mike
| [reply] |