Java and SNA: A case study

By Matt MacKinnon, Adam King, David Kaminsky
2003-05-24

Footnotes

1/3 cup butter, 2T water, 2T vinegar, 1T worchestershire sauce, 1t sugar, 1t onion salt, 1/2t garlic powder, 1/2t pepper, dash ground red pepper--Betty Crocker's Cookbook, 1989, Western Publishing Company, Inc. Return to text.

[2] Using AnyNet's sockets over SNA function, Web browsers can run over SNA. Return to text.

[3] Lap Huynh, "Performance comparison between TCP slow-start and a new adaptive rate-based congestion avoidance scheme," Proceedings of the IEEE International Workshop on Modeling, Analysis, and Simulation of Computer and Telecommunications Systems, 1994. Return to text.

[4] CPI-C was designed from the beginning to be cross-language-enabled. Clearly, the Java architects did not interact with the CPI-C architects. Return to text.

Note: This paper was originally published as an IBM Technical Report (TR 29.2168).

Tutorial Pages:
» Java and SNA: A case study
» The Java/CPI-C API
» Classic Transaction #1: The Pipe
» Classic Transaction #5: The Database Update
» Native Calls
» Diversion: Native Calls and Applets
» Performance
» CPIC Calls That Have Been Implemented
» Conclusions
» Footnotes

First published by IBM DeveloperWorks

Related Tutorials:
» All about JAXP, Part 1
» Make Database Queries Without the Database
» Load List Values for Improved Efficiency
» 2 Ways To Implement Session Tracking
» A Simple Way to Read an XML File in Java
» Develop Aspect-Oriented Java Applications with Eclipse and AJDT