C
Chad Finnegan
I'm trying to figure out a "best practice" for Web Service development. I'm
building a webservice with only a few exposes methods, but has several
methods internally that used the same instance of an instantiated object.
What I'm wondering, is when the Web Service is instantiated on the
Client-Side... should I instantiate this global server-side object that is
used throughout all the public webservice calls, or should I re-instantiate
the object and destroy for every exposed public method of the webservice.
So I would have to instantiate this global server-side object in the
constructor of the webservice. Hope this makes sense, cause I'm confusing
myself with it as well. Trying to find advantages/disadvantages for
optimization.
Thanks for any feedback and let me know if I need to explain myself better,
-Chad
building a webservice with only a few exposes methods, but has several
methods internally that used the same instance of an instantiated object.
What I'm wondering, is when the Web Service is instantiated on the
Client-Side... should I instantiate this global server-side object that is
used throughout all the public webservice calls, or should I re-instantiate
the object and destroy for every exposed public method of the webservice.
So I would have to instantiate this global server-side object in the
constructor of the webservice. Hope this makes sense, cause I'm confusing
myself with it as well. Trying to find advantages/disadvantages for
optimization.
Thanks for any feedback and let me know if I need to explain myself better,
-Chad