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

[James Clark]

> 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.

I would say the behaviour should be that each message is in its own
sequence.

> 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.

Not so.  All he has to do is set it open once in the clientOptions,
because the message options are defaulted from the client options, and
then open false once in the message options.

The simplest possible way of using RM is one message per sequence. It
may not be optimal or most efficient, but it is undeniably the simplest.
We can support this in a way that provides the simplest possible user
experience: just by setting a single option (reliable=>true), they get
reliability.  If they need something fancier or more efficient, then
they can add more options, but we should provide a maximally simple way
for people to get started.

Think about it from the naive user's point of view: they just want to
send a message reliably.  All this stuff about sequences is
rocket-science for the average PHP user.

James