Comments on: [Podcast] Passing Data Between Layers in SOA Model/Smart Client Application http://www.udidahan.com/2007/07/12/podcast-passing-data-between-layers-in-soa-modelsmart-client-application/ Enterprise Development Expert & SOA Specialist Thu, 11 Mar 2010 11:59:32 -0600 http://wordpress.org/?v=2.8.4 hourly 1 By: Hans van Dodewaard http://www.udidahan.com/2007/07/12/podcast-passing-data-between-layers-in-soa-modelsmart-client-application/comment-page-1/#comment-3393 Hans van Dodewaard Sun, 22 Jul 2007 14:45:09 +0000 http://udidahan.weblogs.us/2007/07/12/podcast-passing-data-between-layers-in-soa-modelsmart-client-application/#comment-3393 Udi, Thanks a lot. I spent a few hours to read the post about “Realistic Concurrency” and its links. This has helped me a lot. Udi,

Thanks a lot. I spent a few hours to read the post about “Realistic Concurrency” and its links. This has helped me a lot.

]]> By: thesoftwaresimplist http://www.udidahan.com/2007/07/12/podcast-passing-data-between-layers-in-soa-modelsmart-client-application/comment-page-1/#comment-3295 thesoftwaresimplist Wed, 18 Jul 2007 10:21:59 +0000 http://udidahan.weblogs.us/2007/07/12/podcast-passing-data-between-layers-in-soa-modelsmart-client-application/#comment-3295 Hans, I'm not sure I understand your first question. Transactions, and their corresponding isolation levels are managed within the service. Smart clients just send messages to the service. In terms of concurrency, I suggest you take a look at this post: http://udidahan.weblogs.us/2007/01/22/realistic-concurrency/ If your domain involves very high collaboration between users on a single set of data, you really need to take a look at higher-level architectural patterns like Blackboard. Transactions and such are too low level to adequetly model the complex domain of inter-user coordination and collaboration. Hans,

I’m not sure I understand your first question. Transactions, and their corresponding isolation levels are managed within the service. Smart clients just send messages to the service.

In terms of concurrency, I suggest you take a look at this post:

http://udidahan.weblogs.us/2007/01/22/realistic-concurrency/

If your domain involves very high collaboration between users on a single set of data, you really need to take a look at higher-level architectural patterns like Blackboard. Transactions and such are too low level to adequetly model the complex domain of inter-user coordination and collaboration.

]]> By: Hans van Dodewaard http://www.udidahan.com/2007/07/12/podcast-passing-data-between-layers-in-soa-modelsmart-client-application/comment-page-1/#comment-3195 Hans van Dodewaard Sun, 15 Jul 2007 20:43:19 +0000 http://udidahan.weblogs.us/2007/07/12/podcast-passing-data-between-layers-in-soa-modelsmart-client-application/#comment-3195 But what about (application)transactions, isolation levels and locking in the communication between the services and (smart)clients? If two ore more clients can update the same address we have to choose an isolation level and a lock strategy (first one wins, last one wins, etc.). Last one wins is simple but if we want to choose for optimistic or pessimistic locking, how can we do this? But what about (application)transactions, isolation levels and locking in the communication between the services and (smart)clients?
If two ore more clients can update the same address we have to choose an isolation level and a lock strategy (first one wins, last one wins, etc.).

Last one wins is simple but if we want to choose for optimistic or pessimistic locking, how can we do this?

]]>