OpenLoad Components

  $Revision$
  $Author$
  $Date$
 

Table Of Contents

Change History
Scope
Diagram
[1] Socket
[2] Event Loop
[3] HTTP Client
[4] Test Execution
Files

Change History

  $Log$
  Revision 1.3  2001/06/05 13:14:42  pjohnsen
  fixed anchors for konqueror

  Revision 1.2  2001/03/01 23:37:21  pjohnsen
  Added Developer Info

  Revision 1.1  2001/03/01 22:40:10  pjohnsen
  Initial version

 

Scope

This is a description of the top level components of the OpenLoad project. This should give a good overview of the different parts.

Diagram

[1] Socket

The socket component handles the interface to the socket layer (WinSock for Win32). Sockets are used asynchronously, i.e. there are no blocking calls. This means that the socket component is implemented as a state machine.

The component provides interfaces for:

• Connecting to a foreign host.
• Sending a buffer or string.
• Reading a buffer or line.
• Closing the socket

Each of this operations provide a callback at completion.

[2] Event Loop

The event loop listens for incoming events from the registered sockets. Events are:

• Socket connected to remote host.
• Data arived on a socket.
• Socket is ready to send more data.
• An error occured on a socket

The event loop continously receives events (by calling the select function), and dispatches the arriving events to the cooresponding socket objects.

The component provides interfaces for:

• Adding a socket to the event loop
• Removing a socket from the event loop
• Running the event loop

[3] HTTP Client

The HTTP client implements the HTTP protocol on top of the socket component, i.e. it sends HTTP requests to the web server under test and receives and interpretes the HTTP responses. This is also implemented as a statemachine. The component also handles HTTP headers (request and response) and URLs.

The component provides interfaces for:

• Parsing URLs
• Managing a list of HTTP headers, i.e. adding, removing, finding and iterating over individual headers
• Sending a HTTP request and receiving the response. A callback function is called when the request completes with information about the response, status, etc.

[4] Test Execution

This is the main program that actually executes the test. It works by starting the requested number of simultanous HTTP requests and then entering the event loop. Every time a request completes a callback function is called which updates the statistics (increments the count of transactions, notes the response time, etc.) and each second output is generated.

Files

[1] Socket

  sock.h
  sock.cpp
 

[2] Event Loop

  event_loop.h
  event_loop.cpp
 

[3] HTTP Client

  url.h
  url.cpp
  http_headers.h
  http_headers.cpp
  http_client.h
  http_client.cpp
 

[4] Test Execution

  http_test.cpp