http://www.udidahan.com/2008/04/11/wcf-smart-clients-and-deadlocks/ Enterprise Development Expert & SOA Specialist Sat, 11 Feb 2012 15:16:10 -0600 http://wordpress.org/?v=2.8.4 hourly 1 http://www.udidahan.com/2008/04/11/wcf-smart-clients-and-deadlocks/comment-page-1/#comment-28953 udidahan Sat, 09 Aug 2008 21:33:54 +0000 http://udidahan.weblogs.us/2008/04/11/wcf-smart-clients-and-deadlocks/#comment-28953 Joe - I think that the motivation is race conditions and deadlocks in the UI when interacting with a service (not logging); not that I agree with the solution. Joe – I think that the motivation is race conditions and deadlocks in the UI when interacting with a service (not logging); not that I agree with the solution.

]]> http://www.udidahan.com/2008/04/11/wcf-smart-clients-and-deadlocks/comment-page-1/#comment-28885 Joe Smith Fri, 08 Aug 2008 11:26:58 +0000 http://udidahan.weblogs.us/2008/04/11/wcf-smart-clients-and-deadlocks/#comment-28885 Sorry, but Services should NOT have a user interface to begin with. If it needs to log information it should do so in a file with an exclusive write and shared read and then have another interface that interacts with that file. Even if I have to host in a UI app, I can use a different thread. This is server 101. I can't believe I'm reading this. Sorry, but Services should NOT have a user interface to begin with. If it needs to log information it should do so in a file with an exclusive write and shared read and then have another interface that interacts with that file. Even if I have to host in a UI app, I can use a different thread. This is server 101. I can’t believe I’m reading this.

]]>