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

[James Clark]

On Fri, 2006-12-15 at 17:25 +0600, Samisa Abeysinghe wrote:
> James Clark wrote:
> >> 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.
> >   
> But should we not support 1 if we are to be backward compatible with 
> SOAP ext?

As far as compatibility is concerned, our goal is to be able to
implement the ext/soap API (as a thin layer) on top of our API. This
includes implementing the ext/soap support for dynamic invocation.  But
we can do this regardless of whether we choose 1 or 2 for our API.

James