Re: APPC APIs in TCP/IP CAw95

[Vern Hamberg <hambergv@xxxxxxxxxxxxxx>]

Guillermo

At 04:52 PM 2/23/98 +0100, you wrote:
>Vern,
>
>All the peoples speak really bad about anynet...
>
>only curious in this moment all the "competence" programmers are in luck.
>
>all ours defending the IBM environment, programming APPC and so on and now
>we are the losers!
>
>my main interest is in the substitute APIs from IBM, but some information
>is that the new IBM developing only works with the IBM CAw95.
>
>yes i need some provisional to take time to change to sockets.

AnyNet is a good thing, but it is slower because it converts one protocol
to another. That is, in order to run APPC over IP, it converts APPC (SNA)
packets to TCP/IP packets and then converts back again at the target. Or,
to use IP on an SNA connection, it converts from IP to SNA packets at the
source and the other way at the target.

This is an extra layer of code that has to run for every packet, so things
get slower.

It is too bad that IBM decided to use different APIs in CA95/NT, not the
EHLLAPI set. Makes conversion more difficult. Historically, the new API
names come from the OS/2 versions of Client Access, I think.

HTH (hope this helps)

Vernon Hamberg
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN 55401
(612) 371-1111 x480


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---