[Standards] publish+configure again

[Olivier Goffart]

Le vendredi 30 mars 2007, Peter Saint-Andre a écrit :

> 2. Support publish+configure for all publishes. If the node does not
> exist on publish, the server shall create the node and apply the
> specified configuration. If the node already exists on publish, apply
> the specified configuration.

Personally, I prefer this.
It make the client very simple.

>
> 3. Support publish+configure only on first publish. If the node does not
> exist on publish, the server shall create the node and apply the
> specified configuration. If the node already exists on publish, the
> server shall publish the item only if the configure part of the
> publish+configure matches the existing node config, otherwise it shall
> return an error ("config-does-not-match") and the client must complete
> the normal flow for modifying the node config before the item can be
> published.

This doesn't make client simple if the normal flow must still be implemented

I would say it make auto-create useless since it force you to implement the 
complete flow

( there is no real differences between

->  publish + configure
<-  error  config-does-not-math
->  configure
->  publish

and

-> publish
<- error  node-does-not-exist
-> create + configure
-> publish

)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.jabber.org/pipermail/standards/attachments/20070402/533119c1/attachment.pgp