Hi M,

Passing by-value is what the SCA specifications (see
say should be the calling semantics for remote services.  SCA in PHP
treats all services as remote and assumes local by-reference calls
will just be done using the normal features of PHP.

Passing by-value is a good practice for remote service calls because
it helps with decoupling the two environments by not relying on
sharing instance data.

I'm afraid I don't fully understand the scenario you're describing.
Would it be possible for you to post an example WSDL and a description
of what you think needs to be supported?

Regards, Graham.

On 18 Sep, 16:59, mbertazz <[EMAIL PROTECTED]> wrote:
> Hi all,
> i've a question about passing parameters by reference and not by
> value.
> I'm using WS binding to talk with a remote service. I can't change or
> ask to change that remote service and it use a "by reference"
> approach.
> Is there some way to use SCA impl. in this particular case?
> I think it's not a useful way to force access to private attribute of
> returned object...
> I read this sentence in SCA documentation:
> "How parameters are always passed by value (and not by reference)
> between components, even when the calls are local. This ensures that
> the semantics of a call do not change depending on the location of a
> component."
> I can agree, but can you explain me deeply WHY "passing by reference"
> is not supported so i can be more "strong" defending it?
> Thank you in advence
> M

You received this message because you are subscribed to the Google Groups 
"phpsoa" group.
To post to this group, send email to phpsoa@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 

Reply via email to