In a large scale web service project, it is a good idea to group the services
into logical units. So for example:
http://myservices/CustomerService.asmx
http://myservices/SupplierService.asmx
http://myservices/EmployeeService.asmx
have functions for Customer, Supplier and Employee related tasks
respectively. So far, so good.
Now consider that these services have to be used in a ASP.NET web
application and I want the service URL to be dynamic (i.e. it will be set via
web.config). In the current scheme of things, I need to have 3 entries in
web.config for these 3 service URLs and I also need to add 3 web references.
Is there a better way to do this? Is it possible to refer to just
"http://myservices" and maybe have a single file that will describe all the
services (3 in this case)? In this simple scenario, there are just 3 service
groupings, but if the number climbs to say 20, then maintenance of web.config
and references will be a nightmare.
All suggestions are welcome.
