Hi,
We are a small application development group. We have about 100 Users who
primarily use Microsoft Related Products.
Our Application Development was purley based on a CLient Server Model using
Visual Basic and SQL Server.
We plan to move forward to the .NET environment.
We plan to develop applications with ASP.NEt as well as VB.NET.
Right now we have some COM components or DLL's that we use. For example we
have a DLL called the DSNP Server which is consumed by all our applications.
The function of this is to return DataBase Connection Information for each
application.
We are planning to replace this by a WebService.
1) My first question here is : Do you think the web Service is something
ideal forthis type of functionality.
2) We also need our applications to discover this web Service dynamically so
that if the server hosting this web service goes down we dont need have to
recomiple all our applications to discover this web service. We had planned
to Use Microsoft UDDI Services to accomplish this.
DO you think UDDI Services is an ideal solution for this or is it a over
kill ? What is a good solution.
We eventually plan to use WebServices for other things to where we want to
share information across different systems for example share human resource
information to an application for time cards etc..
I would appreciate if someone could throw some light on this. This would be
of immense help.
Thanks,
Jothi