I see that ReleaseProxy is now obsolete and there is not storage to cache created proxies.
Does this impact performance in some deployment scenarios (local v. app server v. web server) ?
We had to stop caching the proxy to allow for the async data portal behaviors. And this was wise anyway, I think, because I know some people were already using their own BackgroundWorker or other techniques to make multiple overlapping data portal calls, and that was just plain dangerous.
I don't think there's a real perf issue. If you look at nearly all service code out there (for WCF, asmx, Remoting, etc) you'll see that people create/release proxy objects all the time. No one thinks about caching these objects. It was a very minor optimization that now has a pretty significant downside because it blocks safe async implementations.
Copyright (c) Marimer LLC