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

[nandika]

hi all,

For adding reliable messaging support to we need to add following.

*Client Side*

Additions to WSClient  Options array.

1) Enabling RM and specifying RM version
 
"reliable" => TRUE | 1.0 | 1.1

1.0 for RM  version 1.0
1.1 for RM  version 1.1
Default RM version will be 1.1 , If user specified TRUE , rm  version 
will be 1.1.

In addition , user should have specified required addressing options for 
RM to be enabled.

2) Whether to offer a response sequence.

"offer" => TRUE | FALSE

Default value is FALSE.


3) Identifier for sequence

"Identifier" => "unique identifier key"

If this is not specified, a key will be generated internally.

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.

We came up with three possible options.

    i) add a functions setLastMessage(TRUE|FALSE) to WSClient
          default will be FALSE

    ii) add a function setOption() to WSClient.
        setOption(array of options)

    iii) add an optional argument array to WSClient's   'request' and 
'send' functions so that request
        and send functions will be as.
                       request( mixed payload [, array of options])      
                
                       send( mixed payload [, array of options])
          
           -this allows us to  specify this 'request | send ' specific 
options.

  All of these allows us to specify to the WSClient object to send the 
"TerminateSequence" after the application message.
   If we go for one of last two, we can use
            "lastMessage"=> TRUE | FALSE    for the options array 
specify that current application message is the last message

    What is the better solution or is there a better way of doing this ?


*Server Side
*
Additions  to WSService object constructor's options array

To engage RM for server side
"reliable"=> TRUE

addressing should also be engaged.


Thanks,
Nandika


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://wso2.org/pipermail/wsf-c-dev/attachments/20070204/deea1a1d/attachment.htm