×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From: Dr Syd Nicholson
The web service(s) I have created in IceBreak work very well and
very fast ...
I appreciate your endorsement of IceBreak, but it still sounds like you and I are out of sync, regarding what constitutes a web service. And that seems to be a common problem. The term "web service" seems to be applied overly broadly to any process that makes HTTP requests, or generates HTTP responses. But the standards bodies try to limit the term to more specific protocols, using WSDL files, SOAP messages, and XML, etc.
Actually, I don't understand web services protocol that well, myself. I think Aaron Bartell and Scott Klement understand it a lot better than I, for example. Perhaps like you, I'm much more familiar with HTTP protocol, where data is exchanged using little more than &name=value pairs, and prefaced by HTTP request or response headers.
For the sake of this discussion, I'd suggest that we stick to web services that implement WSDL, SOAP, XML, specifications, etc. Does IceBreak generate or consume WSDL files, for example? Have the folks who created IceBreak written anything to consume Web services?
Nathan.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
