 |
- Author:
- JJR (IP: 207.194.36.210)
- Timestamp:
- 12/02/07 06:05:56 (16 years ago)
- Comment:
updates -- cleanup
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ChapterNetworking
| v16 |
v17 |
|
| 37 | 37 | == tango.net.Socket == |
|---|
| 38 | 38 | |
|---|
| 39 | | In Tango this class represents a BSD Socket equivalent. In that sense, it is a low level network interface in Tango: despite simplifying the interface of the BSD Socket in general, using it still requires a descent knowledge of the BSD mechanism. For a more thorough discussion of network sockets, see the references at the end of this chapter. Later, this chapter will introduce high level network interfaces that eliminate much of the hassle of working with low-level sockets. |
|---|
| 40 | | |
|---|
| 41 | 39 | Like the name implies, a socket is a medium for connecting one entity to another. The entities involved are always processes (software running on an operating system) that may exist on local or distributed network nodes (computers). Each process must create a socket in order to establish a communication portal. From the application perspective, the location of the communicating nodes is unimportant so long as the nodes are members of an operational network. Since the socket interface facilitates a form of distributed communication, the mechanism is often referred to as interprocess communication (IPC). |
|---|
| 42 | 40 | |
|---|
| 43 | | A data collection that is sent or received in this model is called a packet. A packet contains useful information that one processes delivers to another for further processing. Examples of packets would be anything from email's sent out on the Internet to web pages being downloaded from a distant server. |
|---|
| 44 | | Though packets may be almost any size, practicality in network communication design dictates that information transferred must be broken up into smaller parts before transmission. While the application may see the received web page as a whole, lower level layers will usually partition large payloads into smaller. These packets are sections of the whole transmitted in designated byte sizes.(CLEANUP) |
|---|
| | 41 | Data that is sent or received in this model is called a packet. A packet contains useful information that one processes delivers to another for further processing. Examples of packets would be anything from email's sent out on the Internet to web pages being downloaded from a distant server. Though packets may be almost any size, practicality dictates that information transferred must be broken up into smaller parts before transmission. While the application may see the received web page as a whole, lower level layers will usually partition large payloads into smaller. These packets are sections of the whole transmitted in designated byte sizes. |
|---|
| | 42 | |
|---|
| | 43 | In Tango the Socket class constitutes a complete wrapper for the BSD Socket API. In that sense, it is a low level network interface in Tango: despite simplifying the interface of the BSD Socket in general, using it still requires a thorough knowledge of the BSD mechanism. Here we will give an overview of how to apply the Tango Socket mechanism. For a more thorough discussion of network socket specifics, see the references at the end of this chapter. In later sections, this chapter will introduce high level network interfaces that eliminate much of the hassle of working with low-level sockets. |
|---|
| 45 | 44 | |
|---|
| 46 | 45 | == More than Sockets == |
|---|
|
 |
 |
|
 |
Copyright © 2006-2024 Tango. All Rights Reserved. | Page Width:
Static or
Dynamic
