Changes between Version 3 and Version 4 of Old/Documentation/OTG/FuncSpec/Gate

Timestamp:

Apr 4, 2006, 9:24:43 PM (18 years ago)

Author:

zhibinwu

Comment:

—

Old/Documentation/OTG/FuncSpec/Gate

@@ -3 +3 @@
 = Gate =
 
-[source:otg/trunk/src/cpp/gate.h#latest Gate] is an abstract class for the interface to receive a packet, whether UDP, TCP Socket, or LIBMAC inteface. 
-The most basic virtual funciton for a gate is defined here:
+[source:otg/trunk/src/cpp/gate.h#latest Gate] is an abstract class for the interface to receive a packet, whether UDP, TCP Socket, or LIBMAC interface. 
+The most basic virtual function for a gate is defined here:
  * receivePacket
-Genereally, the OTR architrecture assume one OTR could have more than one gates. Each gate is bound to only one port number. Thus, if there are multiple ports used to receive packets, there are multiple gates. There is only one thread associated with each gate. One gate, one thread. The gate could have multiple flows, but unlike [source:otg/trunk/src/cpp/port.h#latest Port], "Gate" is in charge of reception, and ''Flow'' is passive, associated with one sender address.
+Generally, the OTR architecture assume one OTR could have more than one gates. Each gate is bound to only one port number. Thus, if there are multiple ports used to receive packets, there are multiple gates. There is only one thread associated with each gate. One gate, one thread. The gate could have multiple flows, but unlike [source:otg/trunk/src/cpp/port.h#latest Port], "Gate" is in charge of reception, and ''Flow'' is passive, associated with one sender address.
 
 [[Image(classGate.png)]]
 
-== Demultiplexing incoming packets ==
+== De-multiplexing incoming packets ==
 
 A link table data structure is used to store the sender information of all received packets. Each entry of sender information is defined as a class [source:otg/trunk/src/cpp/flow.h#latest Flow].
@@ -28 +28 @@
 
 To initialize the Gate object, there are two functions need to be called.
- * '''init''': the implemenatation of this depends on different child classes.
+ * '''init''': the implementation of this depends on different child classes.
  * '''configGate''':  this is used to bind the Gate object to the [source:otg/trunk/src/cpp/orbitapp.h#latest OrbitApp] and [source:otg/trunk/src/cpp/sink.h#latest Sink] objects.
- * '''startReceive''': when a Gate thread (receiving thread) is initialzied by the OTR main function, this function is called to do final preparations.
+ * '''startReceive''': when a Gate thread (receiving thread) is initialized by the OTR main function, this function is called to do final preparations.
 
 == Receive Operation ==
 ''receivePacket'' is a virtual function for packet reception operation.
-In general, receivePacket are occured in a per-packet basis. After it is called, for TCP sockets, recv() functons. For UDP and RAW sockets, recvfrom() functions are used to receive data.
-It is in the default blocking socket mode. So, when ''recv'' and ''recvfrom'' socket functuon is called, unless some packets or bytes are retrieved, this thread is blocked.
+In general, receivePacket are occurred in a per-packet basis. After it is called, for TCP sockets, recv() functions. For UDP and RAW sockets, recvfrom() functions are used to receive data.
+It is in the default blocking socket mode. So, when ''recv'' and ''recvfrom'' socket function is called, unless some packets or bytes are retrieved, this thread is blocked.