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

[Damitha Kumarage]

James Clark wrote:

>>3) Identifier for sequence
>>
>>"Identifier" => "unique identifier key"
>>
>>If this is not specified, a key will be generated internally.
>>    
>>
>
>What does this do from the user's perspective?  Is it to allow them to
>make subsequent messages be part of the same sequence?
>  
>
If the user need to send messages to the same service in two sequences 
at the same time
then he need to differentiate these two sequences by providing different 
sequence keys.
If he do not provide a sequence key a sequence key is generated 
internally. Even in this case
his subsequent messages will be part of the same sequence until he 
terminate the sequence.

>  
>
>>4)
>>Need a way to specify when to send the "TerminateSequence" message.
>>This we can't do with options array as this option should be set after
>>multiple calls to
>>$client->request() function.
>>    
>>
>
>But doesn't our API already allow us to specify options on a per-message
>basis by passing a WSMessage to send/request)?
>
>We should make the simplest thing easy.  The simplest thing is to send a
>sequence with one member.  So if you don't specify any options (other
>than reliable), the sequence should be terminated after the first
>message.  In other words, the default for lastMessage should be true.
>Given this, it might be better to invert the sense of lastMessage, and
>have an option whose meaning is "keep the sequence open", defaulting to
>false, maybe "willContinueSequence" or "toBeContinued" or something like
>that.
>  
>
This depends on the way one is using RM. If one normally need to
send several messages in the same sequence then from the php
user perspective he need to repeatedly set the option that sequence is 
"open"
until the last message he send where on the other hand if he use
"lastMessage" he need to set the option only once.

Damitha