|
There is nothing as such wrong with doing web service calls using other protocols than http, and others may perform better.
Once you understand what exactly has to happen for a web service call, it's pretty obvious that it isn't going to perform well (especially for chatty applications like the above mentioned app). First, you have the CPU and memory usage to build up a pretty bloated XML document and then you have to open a connection to an HTTP server that has to pass all that data to another application (more memory and CPU). That application has to then translate that XML file into what ever type of data structure it needs to deal with (yet more memory and CPU), do what ever it has to do (memory, CPU, other I/O), build up another XML document with its response (more memory and CPU), and send that back to the caller which will most likely then convert it into its own data structures. What about that process sounds like it's good for doing inter process communications?
As an Amazon Associate we earn from qualifying purchases.
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.