RE: WCF concurrent call on client
- From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng[MSFT])
- Date: Mon, 10 Dec 2007 04:29:01 GMT
{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\lang2052\f0\fs20 Hi Daniel,
\par
\par As for WCF client proxy, it seems a bit different from previous webservice client proxy class. WCF proxy is somewhat a heavy-weight one which means if we'll frequently issue method call in concorrent threads, it would be costly to always create a new proxy instance when making a method call. Here is some blog article which describes manually using a proxy pool to address large concurrent WCF method call case:
\par
\par #WCF Proxy Performance vs WSE V3
\par http://weblogs.asp.net/pglavich/archive/2007/02/24/wcf-proxy-performance-vs-wse-v3.aspx
\par
\par #A Sample for WCF Client Proxy Pooling
\par http://blogs.msdn.com/wenlong/archive/2007/11/14/a-sample-for-wcf-client-proxy-pooling.aspx
\par
\par #Service Instances and Concurrent Execution
\par http://blogs.msdn.com/wenlong/archive/2007/08/10/service-instances-and-concurrent-execution.aspx
\par
\par Sincerely,
\par
\par Steven Cheng
\par
\par Microsoft MSDN Online Support Lead
\par
\par
\par
\par ==================================================
\par
\par Get notification to my posts through email? Please refer to
\par http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
\par ications.
\par
\par
\par
\par Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
\par where an initial response from the community or a Microsoft Support
\par Engineer within 1 business day is acceptable. Please note that each follow
\par up response may take approximately 2 business days as the support
\par professional working with you may need further investigation to reach the
\par most efficient resolution. The offering is not appropriate for situations
\par that require urgent, real-time or phone-based interactions or complex
\par project analysis and dump analysis issues. Issues of this nature are best
\par handled working with a dedicated Microsoft Support Engineer by contacting
\par Microsoft Customer Support Services (CSS) at
\par http://msdn.microsoft.com/subscriptions/support/default.aspx.
\par
\par ==================================================
\par \tab
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par \pard\li720 --------------------
\par From: =?Utf-8?B?RGFuaWVs?= <daniel.shen@xxxxxxxxxxxxxxxx>
\par Subject: WCF concurrent call on client
\par Date: Sun, 9 Dec 2007 17:50:00 -0800
\par Hi,
\par
\par I have a winform client which consumes a WCF service. I have a single
\par service client(proxy) at the winform side, but spread the service calls into
\par multiple threads so that they can do works concurrently. My confusion is, as
\par all threads share the same proxy, will one thread block another while calling
\par a long running service? Is this related to the service concurrent
\par configuration?
\par
\par Thanks.
\par
\par Daniel
\par \pard
\par
\par }
- Follow-Ups:
- RE: WCF concurrent call on client
- From: Steven Cheng[MSFT]
- RE: WCF concurrent call on client
- Prev by Date: Re: WCF / J2EE interoperability - DataTable
- Next by Date: WSE032: There was an error loading the microsoft.web.services2
- Previous by thread: receive classes in parameters in web methods
- Next by thread: RE: WCF concurrent call on client
- Index(es):
Relevant Pages
|