Thread View: comp.protocols.ibm
3 messages
3 total messages
Started by mikec
Wed, 04 Nov 1992 14:46
Boycott APPN; Endorse APPI
Author: mikec
Date: Wed, 04 Nov 1992 14:46
Date: Wed, 04 Nov 1992 14:46
13 lines
987 bytes
987 bytes
Basically the title says it all. It's a shame the whole world is becoming more "open" in terms of networking solutions, and then you turn around and take a close look at the world's largest computer corporation to see that all they are trying to do is protect their arcane interests with yet another useless communications protocol. Typical Big Blue. NO FLAMES PLEASE, I believe I represent a majority, not the minority! Mike Catalanotti. #include <std_disclaimer.h>
Re: Boycott APPN; Endorse APPI
Author: "Charles Ganzhorn"
Date: Wed, 04 Nov 1992 21:32
Date: Wed, 04 Nov 1992 21:32
32 lines
2006 bytes
2006 bytes
Both protocols are equally stupid when you consider the impact on the client workstation. And in the case of APPI, gee, IGRP was a great hit: I can get it on SO many routers. (Yeah, right!) Now the strategy that makes sense is to use OSF DCE or at least get IBM to firm up their CPI-C over TCP strategy and then use them to build your "blue" applications. APPN should never leave the computer room. Why should I support dual stacks all over heck IF I get my blue connectivity over TCP? And if I DO decide I have to have APPN to support my IBM applications, then why on earth should I use a tunneling technique rather than a native router? There is a reason they are called multi-protocol routers. Tunneling causes a performance hit and is a kludge by definition. Oh, and by the way, anyone still using IP only routers: get in the real world. Sometimes business reasons force the issue. You use the protocol that makes sense in the homogeneous environment and TCP to bind it all together. I no more expect to remove SNA from my mainframes as I would expect to remove DECnet from my VMS hosts. They each provide functionality that is important to those environment. But that doesn't mean I expect to implement DECnet, SNA, and TCP/IP on all my clients. Let the HOSTS take the burden of running the dual stacks. Use TCP only on the client as much as possible. OK, enough spouting: let the flames begin. Charles. -- Charles Ganzhorn E/Mail: ccganzhorn@mmm.com 3M IS&DP Network Services AT&T: +1 612 736 7122 St. Paul, MN FAX: +1 612 736 7689
Re: Boycott APPN; Endorse APPI
Author: Dave Andrews
Date: Fri, 06 Nov 1992 01:41
Date: Fri, 06 Nov 1992 01:41
11 lines
691 bytes
691 bytes
In article <5814@balrog.ctron.com> mikec@cardinals.ctron.com () writes: > >... a shame ... protect their arcane interests ... useless communications >protocol ... Typical Big Blue. > >NO FLAMES PLEASE Curious how the guys that dish it out can't take it themselves. - David Andrews dandrews@bilver.oau.org
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads