Comments on: Where Do Resources Come From? http://www.subbu.org/blog/2008/10/where-do-resources-come-from Wed, 08 Feb 2012 05:16:45 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: subbu http://www.subbu.org/blog/2008/10/where-do-resources-come-from/comment-page-1#comment-9382 subbu Tue, 04 Nov 2008 18:04:55 +0000 http://www.subbu.org/?p=522#comment-9382 Yes. That is the way to do it. See the slides on Pragmatic REST at http://www.subbu.org/blog/2008/10/slides-from-the-colorado-software-summit, which essentially describes that. Yes. That is the way to do it. See the slides on Pragmatic REST at http://www.subbu.org/blog/2008/10/slides-from-the-colorado-software-summit, which essentially describes that.

]]> By: Nathan Howell http://www.subbu.org/blog/2008/10/where-do-resources-come-from/comment-page-1#comment-9289 Nathan Howell Mon, 03 Nov 2008 05:49:45 +0000 http://www.subbu.org/?p=522#comment-9289 Maybe I'm way off here, but couldn't you just create a single document (on the client) that describes the transaction completely, and POST it to /transactions? Then the transaction can be verified, applied safely, and the accounts updated by some backend process (the details of which don't matter to the interface). I'd be interested to hear thoughts on this. Nathan Maybe I’m way off here, but couldn’t you just create a single document (on the client) that describes the transaction completely, and POST it to /transactions? Then the transaction can be verified, applied safely, and the accounts updated by some backend process (the details of which don’t matter to the interface).

I’d be interested to hear thoughts on this.

Nathan

]]> By: Jean-Jacques Dubray http://www.subbu.org/blog/2008/10/where-do-resources-come-from/comment-page-1#comment-8471 Jean-Jacques Dubray Sun, 26 Oct 2008 16:34:08 +0000 http://www.subbu.org/?p=522#comment-8471 Subbu: I thought, I'd chime in about the last one. a) I find it quite ironic to think that a business process is no more than a series of resources interacting as part of their lifecycle (debit, transfer and credit) and the REST camp is now inventing "process" resources when they would have otherwise the absolute right foundation if only they could understand that resources have indeed a lifecycle made up of states and transitions and that there is indeed an action based "API" to transition resources from one state to another. So please, before you guys mess up the BPM space like Assaf et al in its time, I would urge you to think Resourcefully about it. b) the example that you are providing is extremely interesting from a REST perspective because it shows how impractical the artificial network authority boundary is. Let's say I really want to create a RESTful transfer. How could I go about doing that. I need to 1) POST a "debit" resource to an account 2) POST a "transfer" resource to this debit 3) Let's that somehow you achieve transactionality and you can't create a debit without a transfer and vice versa 4) Now, I need to POST a "credit" resource to the transfer, but does it belong to the transfer resource or the receiving account? How do I achieve transactionality again between the receiving account, the transfer and the credit resource? Now that the transfer has been completed how do you update the debit and credit resources? It would be really interesting to see a full RESTful implementation of this use case. JJ- Subbu:

I thought, I’d chime in about the last one.

a) I find it quite ironic to think that a business process is no more than a series of resources interacting as part of their lifecycle (debit, transfer and credit) and the REST camp is now inventing “process” resources when they would have otherwise the absolute right foundation if only they could understand that resources have indeed a lifecycle made up of states and transitions and that there is indeed an action based “API” to transition resources from one state to another. So please, before you guys mess up the BPM space like Assaf et al in its time, I would urge you to think Resourcefully about it.

b) the example that you are providing is extremely interesting from a REST perspective because it shows how impractical the artificial network authority boundary is. Let’s say I really want to create a RESTful transfer. How could I go about doing that.

I need to
1) POST a “debit” resource to an account
2) POST a “transfer” resource to this debit
3) Let’s that somehow you achieve transactionality and you can’t create a debit without a transfer and vice versa
4) Now, I need to POST a “credit” resource to the transfer, but does it belong to the transfer resource or the receiving account? How do I achieve transactionality again between the receiving account, the transfer and the credit resource?

Now that the transfer has been completed how do you update the debit and credit resources?

It would be really interesting to see a full RESTful implementation of this use case.

JJ-

]]>