> - Some of the other methods in the contract are also confusing in > terms of what they're meant to return. Is it okay if I change the contract a > little bit or is that something we are leaving fixed for the sake of > consistency with the PHP? > >> I'd like to defer to some of the PHP Devs on this one? >> Should the new .net contract be optimized for our new config system, (ie >> disregarding PHP compatability)? >> That may cause additional changes to the PHP contract, when it comes time >> for update the config tab. >> >> In particular we may need to change method parameters, and return types, or >> add change properties on the return objects. >> Also for the case of methods that aren't being used.
I think yes. We should find an optimal mechanism, even if it breaks PHP. We can fix PHP based on agreed contract. >> >> Either way we go it would be helpful to append your proposed service >> contract to STONEHENGE-66? +1. We can review it and agree for a common contract. Regards, Shankar > > > Thanks, > Avantika > -- S.Uthaiyashankar Software Architect WSO2 Inc. http://wso2.com/ - "The Open Source SOA Company"
