On Wed, 08 Mar 2006 10:26:11 -0800, Bobby Rullo <[EMAIL PROTECTED]>
wrote:
2. The "If" header allows you to create two resources in a way that
creating the second one relies on the existence of the first one. The
second PUT would look like this
PUT /users/lisa/work/task-prepare-staff-meeting HTTP/1.1
If: <http://share.o11n.org/users/lisa/work/staff-meeting-event>
([event-etag])
Content-Type: text/calendar
...
There's two options, there may be others.
I'm not sure how that would solve the transactionality problem. If the
second PUT failed, the first one would still remain, no?
Yes, that's true. How to fix atomicity failures might depend on how
exactly they tend to happen -- probably needs more research to see what
the failure case typically is. Having the second PUT depend on the
success of the first might address some or many of those failures or it
might not.
Lisa
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
