Let's assume that I am developing several different projects for different clients. Along the way, I may come up with "service routines" which can be generalized (such as recording some progresss or other info in a database table common to all of the different clients -- separately, of course).
If a WebService a good place to place these? Assuming that everything (database connection, etc.) can be passed in, would there be any reason why such a "service package" shouldn't be deployed in this way?
Hints, suggestions appreciated ... :) KevInKauai
Technically, you can, but unless you have a distributed system what does it gain you?
Why not write a common data layer component to use in all of your projects? This will give you the advantage of re-use without impact on performance.
Web services are very useful, but I doubt if they are necessary in your scenario.
Still not clear about the resusablity issue, Are planning to consume the WebService from all client ajax application?
No comments:
Post a Comment