wcf-proxy

I am considering using a Shared (read static) WCF proxy client for a high throughput application. I believe there is a performance gain in doing this, but I have not benchmarked this as yet. Are there some serious pitfalls to this idea? From my research I can see that there is the issue of handling the fault state, it is not clear what the flow on affect of this state would be to other pending requests. Does anyone have any experience recovering a WCF proxy from it's faulted state? thanks in advance! Once the channel is in a faulted state it will stay that way. So yes, I think a static client

I'm finding mixed answers to my question out in the web. To elaborate on the question: Should I instantiate a service client proxy once per asynchronous invocation, or once per Silverlight app? Should I close the service client proxy explicitly (as I do in my ASP.NET MVC application calling WCF services synchronously)? I've found plenty of bloggers and forum posters out contradicting each other. Can anyone point to any definitive sources or evidence to answer this once and for all? I've been using Silverlight with WCF since V2 (working with V4 now), and here's what I've found. In general, it

Is there anyway I can invoke a WCF service without adding service reference or even having a proxy at all. You can invoke the service using a HttpWebRequest. Example below:- private static XDocument CallSoapServiceInternal(string uri, string soapAction, string contentType, XDocument reqXml) { var req = (HttpWebRequest)WebRequest.Create(uri); req.ContentType = contentType; req.Method = "POST"; req.Headers.Add("SOAPAction", soapAction); req.Credentials = CredentialCache.DefaultCredentials; req.Timeout = 20000; //req.Timeout = System.Threading.Timeout.Infinite; using (var reqStream = req

I have a WCF Client Proxy connected to a third party webservice. The proxy works fine with nearly everything except on function. This function works just fine with a ASMX proxy. I have added service trace logging and can see the response from the service coming back. Only the proxy returns null. So now I know for sure that the proxy is at fault. Where to from here? RESOLUTION I found the issue. WCF is less forgiving than an ASMX proxy. The service WSDL specifies that the returned object was called "data", and the actual xml passed back was called "result" So that was a great goose chase! I