Geeks With Blogs


Add to Google

Tim Hibbard CEO for EnGraph software

The concept of web services is great, and I'm always looking for new ones or new ways to use the power of web services. I made a list of good ones I've found so far

Most developers have their own style of programming, their own dialect. So using another developer's function, to get the result that you are looking for, can be frustrating. Some want you to enter a string and return a structure, some want a string and then return a structure. The documentation for this is usually minimal. Most developers write functions for themselves, so they never think that someone may not understand their intent.

There needs to be a standard for developing and consuming web services. I think a good idea would be that all functions accept a structure for parameter(s) and return a structure. These structures would be appropriately named. Like stcAcceptLocation and stcReturnLocationInfo

So a web service call would look something like this:

stcAcceptLocation.City = "Kansas City"

stcReturnLocationInfo = SomeWebService.GetLocationInfo(stcAcceptLocation)

MsgBox ("Population is " & stcReturnLocationInfo.Population.ToString)

Now we can spend more time using web services instead of figuring out how the developer wanted us to use it!

Posted on Thursday, August 5, 2004 2:33 PM | Back to top

Comments on this post: The problem with web services

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Tim Hibbard | Powered by: