VRXDA: Difference between revisions
Appearance
mNo edit summary |
|||
(2 intermediate revisions by the same user not shown) | |||
Line 13: | Line 13: | ||
* It also means that a distributed application can be developed and tested first on a single machine using OS/2 named pipes and later moved to span a network using NetBIOS or APPC without recoding. | * It also means that a distributed application can be developed and tested first on a single machine using OS/2 named pipes and later moved to span a network using NetBIOS or APPC without recoding. | ||
The Distributed Connection Object supports three communication protocols: | The Distributed Connection Object ([[VRDistributedConnection]]) supports three communication protocols: | ||
;Named pipes: A form of OS/2 interprocess communication that uses file-system calls to transfer data between processes running on the same workstation. Named-pipes connections across a network are not supported. | ;Named pipes: A form of OS/2 interprocess communication that uses file-system calls to transfer data between processes running on the same workstation. Named-pipes connections across a network are not supported. | ||
;NetBIOS: A communications programming interface that supports peer-to-peer connections between applications running on a LAN. | ;NetBIOS: A communications programming interface that supports peer-to-peer connections between applications running on a LAN. | ||
Line 37: | Line 37: | ||
==Links== | ==Links== | ||
* [ | * [vrxda.zip] Version 1.2 - 1995 | ||
[[Category:VX-REXX]] | [[Category:VX-REXX]] |
Latest revision as of 15:24, 15 March 2020
VRXDA object for VX-REXX.
The Distributed Connection Object allows you to create true Client/Server applications with VX-REXX version 2.1 or greater.
The Distributed Connection Object hides the complexity of the supported communication protocols.
- Several methods of interprocess and cross-network communication are available for OS/2. However, each has a different programming interface. This means that a programmer must learn different ways to accomplish the same task, depending on the protocol in use.
- The Distributed Connection Object provides a single, consistent programming interface to any of the three supported communication protocols: OS/2 named pipes, NetBIOS, and APPC by using IBM* Distributed Application/2 services. The programmer must therefore learn only one interface in order to use multiple protocols.
It allows runtime selection of communication protocol.
- Ordinarily, the programmer must decide when writing an application which communication protocol to use. If it becomes necessary to change protocols, the application must be rewritten.
- Because the Distributed Connection Object uses the same APIs regardless of the underlying protocol, the selection of protocol need not be made until run time. This means that the protocol can be changed without access to source code and without recompiling.
- It also means that a distributed application can be developed and tested first on a single machine using OS/2 named pipes and later moved to span a network using NetBIOS or APPC without recoding.
The Distributed Connection Object (VRDistributedConnection) supports three communication protocols:
- Named pipes
- A form of OS/2 interprocess communication that uses file-system calls to transfer data between processes running on the same workstation. Named-pipes connections across a network are not supported.
- NetBIOS
- A communications programming interface that supports peer-to-peer connections between applications running on a LAN.
- APPC
- Advanced Program-to-Program Communication, an implementation of the IBM Systems Network Architecture (SNA) LU 6.2 protocol. APPC allows distribution of applications across an SNA network.
Note: To Use the VRXDA object you must have VX-REXX version 2.1 or greater.
Files
- VRXDA.DLL (The VX-REXX object DLL)
- VDAAPPC.DLL (APPC protocol DLL)
- VDANETB.DLL (NetBIOS protocol DLL)
- VDANETBL.EXE (NetBIOS Daemon)
- VDANP.DLL (Named Pipes protocol DLL)
- VDAOCRW.DLL (Interface DLL)
- VDAPROF.DLL (DLL for profile editor)
- VDAPROF.EXE (Profile editor)
- VDAPROF.HLP (Help for the profile editor)
- IBMDABB.CP (A default profile for your program)
Licence
- Public Domain
- Author: Peter Kanis / ADD Consulting (CH)
Links
- [vrxda.zip] Version 1.2 - 1995