[wsf-c-dev] [wsf-php] RM API

[Samisa Abeysinghe]

nandika wrote:
> Idea was to support  one way messaging with RM 1.0.
Why not support that with RM 1.1 as well? What is the advantage of using 
1.0 to support oneway.
It sounds odd to say "we support one way with RM 1.0 and two way with RM 
1.1". Comparatively, it is better to say that we support RM 1.1.

>>>
>>> In addition , user should have specified required addressing options 
>>> for RM to be enabled.
>> What addressing stuff are required? Can we enable those by default if 
>> RM is in use?
> For addressing, we need       Addressing Endpoint,
>       Addressing Action.
>       replyTo  Endpoint reference with wsa anonymous URI.
>
> Enabling Addressing can be done. but still user should specify the 
> 'To' Endpoint and Action.
> But I think we should expect from the user to know that , addressing 
> should be enabled for RM
> to work.
Yes we can document so. But user would not have to give useWSA option if 
Rm is already in use.
>> "offer" does not indicate that is it talking about  "response 
>> sequence", shall we use "response_sequence" instead?
> Offer is the word used in the specification, So I selected that.
But that is too generic. Most PHP users would never even have a look at 
the speck I suppose. So it better be a meaningful name here :)

>> Also, as we support more and more spec and we introduce more options, 
>> would it not be a good idea to have a prefix to indicate which spec 
>> this option belongs to?
>> e.g. "rm_sequence_identifier",  "rm_response_sequence" etc.
> I agree. But since we have already defined some on our API ( example 
> addressing ). It would be necessary  to change those as well for 
> consistency.
May be we can leave what we have already defined as they are and look 
into new specs that we integrate.
> I think we should select one of  $client->rmTerminate() or adding an 
> optional array to 'request' ,'send' functions.
> I feel that adding an optional array is more consistent with rest of 
> our API.
But how often would we require adding an option to request or send. I 
hardly can think of any other example other than RM.
Would we ever need that with security stuff or with any other spec? If 
not, we would be better off with rmTerminate and not change the current 
API that we have already defined for send and request.

Samisa...