Hi Mark, Mark Baker wrote: > On 7/4/06, Dan Creswell <[EMAIL PROTECTED]> wrote: >> So can you please provide a sketch of how you'd recommend people solve >> this problem in the context of stateless messaging? > > Well, there's many ways one could do it, but as a very simple example, > I could send each message with an HTTP header that said, say, > "Transaction: 91023123", indicating that those messages were to be > considered part of the transaction #91023123. >
Cool - so do we also use headers for signalling commit/abort? Couple of other things also immediately spring to mind: (1) How do you ensure that each client is using globally unique transaction ids? I'm assuming of course I have multiple clients performing concurrent (though not necessarily conflicting) updates. (2) If you happened to be performing a single transaction across more than one site (i.e. the resources you're touching aren't all at one "address" such as www.sun.com), how do you handle commit/abort then? >>From a REST perspective, what matters is that the meaning of the > message is independent of the state of the transaction, unlike with a > session based transaction. > > Mark. > > Cheers, Dan. ------------------------ Yahoo! Groups Sponsor --------------------~--> Check out the new improvements in Yahoo! Groups email. http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
