iTP Secure WebServer System Administrator's Guide (iTPWebSvr 5.1+)

Using NonStop Servlets for JavaServer Pages With
The iTP Secure WebServer
iTP Secure WebServer System Administrator’s Guide—522659-001
9-11
NonStop Servlets for JavaServer Pages in The iTP
WebServer Architecture
By eliminating message-system hops, Parallel Library TCP/IP reduces the total path
length from the application to the wire. This path-length reduction reduces individual
request latency. In addition, more requests per second can be serviced using the same
processor cost, resulting in higher throughput.
In conventional TCP/IP, if you ran multiple process instances of a listening application
in multiple processors (to increase computing power), you needed a different TCP/IP
process (one per listening application process instance) in each processor. Each TCP/IP
processes required a unique physical port (PIF) and presented a unique IP host to the
outside world. Parallel Library TCP/IP allows multiple application process instances
running in different processors to be presented to the outside world as a single IP host,
because by using Parallel Library TCP/IP, you can run multiple process instances of a
listening application in multiple processors, all sharing the same PIF. ServerNet™
allows all processors in a clustered system to access the same PIF; Parallel Library
TCP/IP allows applications in different processors to access the same PIF and share a
common listening TCP port number.