Abstract: Generally, this disclosure describes software delivery systems (and methods). A server is provided that operates to provision software on a customer's local machine. The server system, in response to a software purchase from an end user (customer), is configured to install the software on the customer's machine, encrypt the software, and provision encryption keys to grant the customer access to the software. In addition, a software agent is installed on the customer's machine that enables monitoring, by the server, of the customer's installed software. The server system is configured to control customer access to the installed software, via the software agent, and to terminate customer access to the software (for example, for nonpayment of fees). Thus, the software provider can retain control over software that is remotely deployed at an end user location.

Abstract: Generally, this disclosure describes software delivery systems (and methods). A server is provided that operates to provision software on a customer's local machine. The server system, in response to a software purchase from an end user (customer), is configured to install the software on the customer's machine, encrypt the software, and provision encryption keys to grant the customer access to the software. In addition, a software agent is installed on the customer's machine that enables monitoring, by the server, of the customer's installed software. The server system is configured to control customer access to the installed software, via the software agent, and to terminate customer access to the software (for example, for nonpayment of fees). Thus, the software provider can retain control over software that is remotely deployed at an end user location.

Abstract: In one embodiment, the present invention includes an apparatus having a first interface to process data for communication according to at least first and second protocols, a second interface to process data for communication according to at least the first and second protocols, and a common buffer coupled to the first and second interfaces to temporarily store the data. In another embodiment, a passive interposer includes at least one interconnect. The passive interposer can be coupled to an unpopulated socket of a system to route signals from a first processor to a device coupled to the unpopulated socket. Other embodiments are described and claimed.

Abstract: A communication system featuring a plurality of nodes in which at least one node is implemented with adaptive driver software following a load balancing scheme that takes into account packet characteristics associated with the data traffic load before dynamically distributing the data traffic among multiple communication channels. Of these communication channels, only one channel is allowed to receive data requests and all of the channels are allowed to transfer data packet(s) to the data requesting node.

Abstract: Described is a method and arrangement for managing a network which is coupling at least a first component and a remote component. A database is transmitted from the first component to the remote component via the network. The database includes filter data having at least one condition and action data corresponding to the at least one condition. A data packet is transmitted from the first component to the remote component via the network. The data packet includes a plurality of fields and data. The fields of the data packet are filtered at the remote component to determine if the at least one condition is satisfied.

Abstract: A system and method of by pipelining the flow of data in a bus mastered network controller. The concept of successful completion on copy is used. The bus mastering network controller indicates to the CPU that a frame has been successfully transmitted as soon as the data from main memory is copied across system bus to buffer memory in the controller. The driver layer of the network operating system upon receiving the successful completion on copy signal from bus mastering network controller 16 releases its own transmit frame descriptors and buffers associated with the copied frame which enables the lower protocol layer to initiate a new frame transmission while the previous one is still being transmitted. The CPU and bus mastering network controller do not contend for system bus during the setup of the new frame since bus mastering network controller continues transmission from buffer memory.

Abstract: A system and method of pipelining the flow of data in a bus mastered network controller. The concept of successful completion on copy is used. The bus mastering network controller indicates to the CPU that a frame has been successfully transmitted as soon as the data from main memory is copied across system bus to buffer memory in the controller. The driver layer of the network operating system upon receiving the successful completion on copy signal from bus mastering network controller 16 releases its own transmit frame descriptors and buffers associated with the copied frame which enables the lower protocol layer to initiate a new frame transmission while the previous one is still being transmitted. The CPU and bus mastering network controller do not contend for system bus during the setup of the new frame since bus mastering network controller continues transmission from buffer memory. The bus mastering network controller does not wait for a complete indication to transfer the next frame to buffer memory.

Abstract: A communication system featuring a plurality of nodes in which at least one node is implemented with adaptive driver software following a load balancing scheme that takes into account packet characteristics associated with the data traffic load before dynamically distributing the data traffic among multiple communication channels. Of these communication channels, only one channel is allowed to receive data requests and all of the channels are allowed to transfer data packet(s) to the data requesting node.

Abstract: The basic invention is to define the TBD data structure in the driver layer to be exactly the same as the pointer structure in the TCB fragment structure and to have the TBD pointer in the TxCB point to the TCB fragment structure which is in protocol space. Also, the driver must specify at initialization that physical addresses be loaded into the TCB fragment pointers. This structure then allows the elimination of the TBDs in driver space. They are replaced by the TCB fragment structure. The advantages are that many cpu instructions formerly needed to set up the TBD's and to manage them in memory are eliminated. Also, it is faster to send the fragment structure to the controller than to send the TBDs. This is because the fragment structure is a contiguous array and can therefore go to the controller in burst mode.

Abstract: The basic invention is to define the TBD data structure in the driver layer to be exactly the same as the pointer structure in the TCB fragment structure and to have the TBD pointer in the TxCB point to the TCB fragment structure which is in protocol space. Also, the driver must specify at initialization that physical addresses be loaded into the TCB fragment pointers. This structure then allows the elimination of the TBDs in driver space. They are replaced by the TCB fragment structure. The advantages are that many cpu instructions formerly needed to set up the TBD's and to manage them in memory are eliminated. Also, it is faster to send the fragment structure to the controller than to send the TBDs. This is because the fragment structure is a contiguous array and can therefore go to the controller in burst mode.