Author of <a href="http://www.newsinjector.com" target="_blank" rel="nofollow">NewsInjector</a>
Originally posted by Andres Delrotti:
Is there a better and more efficient way of dealing with a problem like this? Any form of help would be appreciated.
If they really are going to implement a web service, then more than likely you will get passed back a List object back instead of a result set. I suppose they could implement a (slower) way to let you iterate over the set, but I'll stay out of the politics.
But as far as performance, it would be faster to pass the entire set back from the web service, especially if it is on the same server as the database.
Author of <a href="http://www.newsinjector.com" target="_blank" rel="nofollow">NewsInjector</a>
Originally posted by Andres Delrotti:
The entire set from the "search function" or entire set of ALL employees? So if I could have a max of 500 concurrent users accessing the web service, it would be ok to give the web service the burden of doing the search function? rather than letting it retrieve all employees and do the searching on our part?
The disadvantage of the first is, you would always need to access the web service everytime you search while in the 2nd option, you could just do it daily.
Originally posted by Andres Delrotti:
My main problem here is what if I wanted to do a search employee function. Should we let it be a part of the webservice? or just retrieve all employees from the webservice, transfer it to our app memory and do the searching there.
Consider Paul's rocket mass heater. |