wcf - What could be the consequences of declaring method as AsyncPattern on caller side, and OneWay on implementation side -
i have service implementing following contract:
[operationcontract(isoneway = true)] void execute(ilist<someobject> someobjects);
in order avoid stalling on caller side (which taking few seconds when latency high) want change contract async pattern:
[operationcontract] void execute(ilist<someobject> someobjects); [operationcontract(asyncpattern = true)] iasyncresult beginexecute(ilist<someobject> someobjects, asynccallback asynccallback, object state); void endexecute(iasyncresult asyncresult);
the problem: won't able upgrade implementation side, due production limitation.
i ran , found behave expected, except end callback being called when channel closed.
the question is: suffer performance issues, memory leaks, or other issues haven't thought of?
Comments
Post a Comment