[wsf-c-dev] Additions to PHP API to support Dynamic client

[James Clark]

> This seem to be an issue. There are two options available to solve it.
> 1.  rename our existing methods using underscore.
>       ( since there is a requirement for supporting ext/soap extension kind
>         of api this is my prefered option)
> 
> 2.  Introduce a new object for proxy.
>       If we go for this option, please suggest an appropriate name.

I think 2 is cleaner.  I don't see any problem in implementing the
existing ext/soap API as a thin layer on top of an API that separates
the proxy from the client.

What about the multiple interfaces point? Do we need that? You can't do
it with 1.

To make 2 simple, we should also have

- a way to create the proxy object in single step

- a way to get the underlying client from the proxy

How about if we call the class of the proxy object WSClientProxy?  Then
have a getProxy() method on WSClient to return the proxy (with an
optional argument to identify the interface, if we need that).  Then
have a __getClient() method on the WSClientProxy.  Also a WSClientProxy
constructor that is equivalent to calling the WSClient constructor and
then calling getProxy().

I'm not 100% sure about the names yet. I would like to look at some
other APIs to see what terminology they use.

James