LYCOS RETRIEVER 
Harpoon: Models
built 184 days ago
From this operational definition of a flow, Harpoon's architecture begins with the notion of unicast file transfers using either TCP or UDP. Harpoon does not address the packet level dynamics of TCP file transfers. Rather, it relies on the version(s) of TCP running on end hosts to transfer the requested file. Modeling UDP traffic is complicated by the fact that packet emission behaviors are largely application-specific. At present, Harpoon contains three models of UDP packet transfer: a simple parameterized constant packet rate, a fixed-interval periodic ping-pong, and an exponentially distributed ping-pong. The first source type is similar to some audio and video streams, while the latter two types are intended to mimic the standard Network Time Protocol (NTP) and Domain Name Service (DNS), respectively.
Source:
Feature lines are used in Harpoon to capture and retain the important geometric features of a model. These include areas of high curvature and the boundaries (free edges) of model parts. Harpoon will always attempt to retain these features during meshing. Target mesh sizes can be defined on different Fls, or mesh sizes can be specified on the polygons.
Source:
As described in Overview of Harpoon and summarized in distributional parameters, there are five distributions comprising Harpoon's architectural model for TCP flows. Configuration of three of those parameters is described here. Addressing is described in the following section.
Source:
MORE ABOUT
Models