Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!usc!snorkelwacker!ira.uka.de!smurf!nadia!dialog!root
From: root@dialog.stgt.sub.org (Christian Motz)
Newsgroups: comp.os.os2.programmer
Subject: Re: OS/2 Network APIs
Message-ID: <2468@dialog.stgt.sub.org>
Date: 26 Aug 90 10:51:18 GMT
References: <118@mytardis.UUCP>
Sender: uucp@dialog.stgt.sub.org
Reply-To: root@dialog.stgt.sub.org (Christian Motz)
Organization: Dialog Software Development
Lines: 25

>Doug Harvey writes:
>
>> [...]
>>
>>I think APPC would do the job, but APPC imposed quite a bit of overhead,
>>both in terms of running it, and coding the application.

APPC will indeed do the job -- I am not sure what you are referring to
with the overhead. The only real "overhead" with APPC is that you have
to have the Communications Manager up and running. Once  this  is  the
case, the remaining overhead is not really that big.
   Coding an APPC Transaction Program under OS/2 is  not  really  that
big a problem, since the API for it is rather easy to use,  and  with,
let's say 700 lines  or  so  of  code  you  could  write  yourself  an
interface which basically is as easy to use as file I/O  functions  or
sockets under UN*X for that matter.
   The advantage of using APPC is that you do  not  need  yet  another
communications package to achieve the desired functionality.  Besides,
if you are using remote data services in a LAN, CM is up  and  running
anyway, so  you  can  just  as  well  use  it  anyway.  If  anyone  is
interested, I can elaborate on the usage of APPC a bit. Just drop me a
line at the above address and I will get back to you, mailers willing.

--
Christian Motz                                root@dialog.stgt.sub.org