What is the best method to create objects for webservices

Question

hello all,

i have been developing a console application in VS2005 with C#. The application is actually a command line interface which takes some commands as input and utilizes some web-services to process some data with an external device. The web-services are running in the external device and i have .wsdl files which exposes the web-services to my application.

so for e.g to get a counter value from the device through my application, the following command and the following steps are used!

C:\sampleApp> myapp.exe getcounter deviceid=202.15.65.211 

myapp is the application name and the getcounter is the command and deviceid is an option.

This command actually creates a proxy object for the corresponding web-service class and calls out the web-service with the deviceid as given.

And the output may look like

counter 1 = 2345
counter 2 = 1234
etc...


The actual problem is, web-services are classified in to several functional groups and accordingly i have as many wsdl files with classes and namespaces. It really takes more time to create the objects during runtime, according to the entered command( number of commands are also really more).

To be more specific, for e.g. consider the above example:
To get the counter values, web-service named GetCounter() should be called from the device. To call this method a proxy object for the corresponding class is created and then the method is called. The complete process actually takes more time, so i need to speed up the operation. For this, i have come up with a solution, that to create a background service which can create a proxy object for all the classes and when the application is executed, the application will use the existing proxy object from the windows service through remoting. This method was successfully implemented and it is running quite faster than previous method.

I want to know, whether this practice is accepted?
what is the normal method of practice, when large number of web-services are to be accessed more frequently and dynamically through ?

Please suggest me some common and best practices, if the scenario is given to you.....