Browse Prior Art Database

Method And System For Tracking Unique HTTP Transactions Between A Source And A Destination

IP.com Disclosure Number: IPCOM000201279D
Publication Date: 2010-Nov-09
Document File: 2 page(s) / 22K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system for tracking unique HTTP transactions between a source and a destination using a read-only real time listening monitor is disclosed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Method And System For Tracking Unique HTTP Transactions Between A Source And A Destination

Disclosed is a method and system for tracking unique HTTP transactions between a source and a destination using a read-only real time listening monitor. The read-only real time listening monitor passively tracks HTTP content transferred between the source and the destination and identifies unique identifiers in each of the HTTP transactions.

A HTTP transaction includes a HTTP request and HTTP responses corresponding to

the HTTP request. The read-only real time listening monitor tracks the HTTP transaction by tracking the HTTP request and corresponding HTTP responses. The read-only real time listening monitor identifies unique identifiers in the HTTP request and the corresponding HTTP responses. The unique identifiers may be retrieved from contextual data available in the HTTP content of the HTTP transactions. Based on the unique identifiers, tracking Application Programming Interfaces (

APIs) are invoked at

A model for tracked HTTP transactions

between a source and a destination includes two nodes formed by the source and the destination. Subsequently, tracking APIs corresponding to all HTTP transactions between the source and destination will have a common identifier. In an instance of the method and system the common identifier may be created using IP address and port numbers of the source and destination. Since a timestamp parameter cannot be used for uniquely identifying a transaction, a count number may also be used to differentiate between multiple HTTP transactions. In cases when an Application Response Measurement (

ARM) monitor is used,

identify each HTTP transaction.

may also be used. Thereafter, other parameters including vertical stitch list, horizontal link-id, horizontal stitch list and context are assigned to all HTTP transactions between the source and the destination. Finally, all the parameters are used to model the HTTP transactions between the source and the node.

In an instance of the method and system disclosed herein, the tracking APIs are of the following syntax:

Point (timestamp, vertical link-id, vertical stitch list, horizontal link-id, horizontal stitch list, context

)

In the above syntax, point is a measurement point during the life-span of a HTTP transaction.

Various measuring points during the life-span of a HTTP transaction

include, STARTED, FINISHED, OUTBOUND, INBOUND and HERE. STARTED and...