Writing_Network_Capable_Software modified by Boisy Pitre

Boisy Pitre — Fri, 20 Jun 2014 18:50:17 -0000

--- v2
+++ v3
@@ -24,7 +24,7 @@

 If you are writing a network application that will act as a host (or server), then you need to inform the DriveWire server of your intent by calling the TCPListen routine. 

-### Acting Like a Client
+### Acting like a Client

 As a client, your application is interested in connecting to a host on the other end. To do this, call TCPConnectToHost.

Writing_Network_Capable_Software modified by Boisy Pitre

Boisy Pitre — Fri, 20 Jun 2014 18:50:17 -0000

--- v1
+++ v2
@@ -24,7 +24,7 @@

 If you are writing a network application that will act as a host (or server), then you need to inform the DriveWire server of your intent by calling the TCPListen routine. 

-### Acting a Client
+### Acting Like a Client

 As a client, your application is interested in connecting to a host on the other end. To do this, call TCPConnectToHost.

Writing_Network_Capable_Software modified by Boisy Pitre

Boisy Pitre — Fri, 20 Jun 2014 18:50:17 -0000

Introduction
Using the Network Library
Example Applications

Introduction

DriveWire's approach to networking is to let the server do the "heavy lifting" of the TCP/IP stack and shift the burden away from the CoCo. This lets software developers enjoy the convenience of sending simple commands to initiate an outgoing connection or listening for an incoming one. If you compare getting a network application up and running under NitrOS-9 and DriveWire vis a vis other operating systems, you will quickly see that it is much easier on your CoCo using this method.

The steps for obtaining and using a netork resource under NitrOS-9 consists of these basic steps:

Obtain a path to a network device Set up the port by sending appropriate messages to the server on the path Perform subsequent reading and writing to the path to pass data

Using the Network Library

For convenience, a network library has been written to provide application writers with some common routines for network access. The library is written in assembly language and requires developers to use the RMA assembler and RLINK linker when writing their applications.

Getting a Path

To obtain a path to the network, your program needs to call the TCPOpen routine. The path number of the network path is returned in register A.

Setting up the Path

Depending on whether your application is a client or server, you will want to call one of the following routines: <p> TCPConnectToHost <p> TCPListen

Acting like a Host (Listening)

If you are writing a network application that will act as a host (or server), then you need to inform the DriveWire server of your intent by calling the TCPListen routine.

Acting a Client

As a client, your application is interested in connecting to a host on the other end. To do this, call TCPConnectToHost.

Example Applications

The best way to learn is to look at existing code. For an example of writing a host application, see the inetd.a source code. For a client application, see the telnet.a source file.

Recent changes to Writing_Network_Capable_Software

Writing_Network_Capable_Software modified by Boisy Pitre

Writing_Network_Capable_Software modified by Boisy Pitre

Writing_Network_Capable_Software modified by Boisy Pitre

Introduction

Using the Network Library

Getting a Path

Setting up the Path

Acting like a Host (Listening)

Acting a Client

Example Applications