"sridhar" <sr*****@discussions.microsoft.comwrote in message
news:CF**********************************@microsof t.com...
Hi john,
Let me explain you, my requirement
we are going to develop a web application that has to communicate with a
data vendor through their webservice for some specific evaluation.
Typicall we may have around 8000 transactions per hour.
I understand that for every transaction we are going to hit the webservice
through the proxy class instance and evaluate our data and save the
response.
so i wonder can we adopt any best practise that makes the process simple
and
efficient.
My suggestion is to do nothing special. That will be simple, as you
requested.
If it turns out not to be fast enough, you can then address "efficient". But
you will be working on the efficiency of a working piece of code, instead of
working on both efficiency and functionality at the same time.
With any luck, you will even have developed automated tests for your working
code, so that you will be able to use those tests during performance
enhancement, to determine whether or not your performance enhancements have
broken your code.
This is not COM. You should not expect a major performance hit to
instantiate a web service proxy class. You are much more likely to break
your code by trying to do something fancy to solve a performance problem
which may not actually exist.
Good Luck,
John
