When evaluating the choices also keep in mind the consumer of the
"service." It's going to be much easier from the client to consume a
service from a web-server (Apache) than it will be to code socket-level
communications to a custom socket-listener program... Sure the
web-server approach requires more code on the client side, but all that
code is already written in a class somewhere so calling a service on a
web-server is one or two lines of code, where calling (correctly) a
custom-socket program is more.

I'd go w/Apache w/out a second thought.

-Walden

PS. "service" above means just a page that the other machine calls that
returns a pre-determined dataset, not necessarily a SOA web-service
w/WSDL and all that jazz, although a web-service is the "right" way to
do this.

--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.