COMPUTER SOFTWARE LOAD BALANCING

Brand Owner (click to sort) Address Description
BIG/OS F5 Labs, Inc. 200 First Avenue W., Suite 500 Seattle WA 98119 computer software for load balancing of TCP/IP service requests across an array of servers;
ENVOY Coyote Point Systems, Inc. 56 Main Street, P.O. Box 480 Millerton NY 12546 computer software for load balancing global computer information network services on local and wide area networks; for computer software for managing clusters of server computers; for computer software for managing TCP/IP connections between global computer information network and local and wide area networks;
GUIDEPOST NETGUARD, INC. 2445 Midway Road #2 Carrollton TX 75006 COMPUTER SOFTWARE FOR LOAD BALANCING, ACCESS CONTROL, BANDWIDTH MANAGEMENT AND MONITORING IN A COMMUNICATIONS NETWORK AND USER MANUALS SOLD AS A UNIT THEREWITH;GUIDE POST;
INTELISON REVERB NETWORKS, INC. Suite 105 20099 Ashbrook Place Ashburn VA 20147 computer software for load balancing algorithms of telecommunication networks;
OCTAVIA OPENSTACK FOUNDATION 1214 W 6th Street, Suite 205 Austin TX 78703 Computer software for load balancing in the field of cloud computing infrastructure;The name OCTAVIA does not identify a living individual.;
OCTAVIA Balukoff, Stephen 119 Pine Street, Suite 200 Seattle WA 98101 Computer software for load balancing in the field of cloud computing infrastructure;The name OCTAVIA does not identify a living individual.;
PERFORMABEAMS REVERB NETWORKS, INC. Suite 105 20099 Ashbrook Place Ashburn VA 20147 Computer software for Load Balancing Algorithms of telecommunication networks; Graphical user interface software;PERFORMA BEAMS; PERFORMANCE BEAMS;
 

Where the owner name is not linked, that owner no longer owns the brand

   
Technical Examples
  1. A method and system for auditing software systems by monitoring the use and non-use of software programs in a computer. An operating system of the computer controls execution of software products through the invocation of respective load modules thereof. A monitor is periodically triggered to collect load module execution information, which is filtered by a filtering module, and a correlator correlates load module execution information with data that associates load module names with corresponding software products and develops a list of products executed in the computer over the course of a given time period.