28.06.2013 Views

Papers in PDF format

Papers in PDF format

Papers in PDF format

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Aria.monitor is comprehensive with regard to the data it can capture <strong>in</strong>clud<strong>in</strong>g, if desired,<br />

all of the data from an HTML Form be<strong>in</strong>g transmitted between the Web Client and the<br />

Server. The follow<strong>in</strong>g categories of data are captured:<br />

• Client Request Data<br />

The data captured by the Aria.monitor with regard to the Client Request <strong>in</strong>cludes<br />

the type of browser be<strong>in</strong>g used by the Web client, the authenticated user ID if the<br />

server requires it, the IP address of the client, any references to a previous page,<br />

the allowable response methods, and the acceptable data types that user can view.<br />

• Client Post Data<br />

In many website <strong>in</strong>teractions, the user often enters field data <strong>in</strong>to an HTML Form.<br />

Aria.monitor captures the body content of this data filled <strong>in</strong> by the user. This is<br />

key <strong>in</strong> certa<strong>in</strong> applications, especially where the user is provid<strong>in</strong>g demographic data<br />

or a profile of his or her preferences. Applications can use this data to provide a<br />

personally customized view of their content to the user based on match<strong>in</strong>g the user<br />

ID with previously stored profiles and/or preferences.<br />

• Server Response Data<br />

The data captured by Aria.monitor with regard to the server response <strong>in</strong>cludes<br />

location of source requested (could be another server), the hostname of the server,<br />

the date of last modification, any server def<strong>in</strong>ed directives, the expiration date of<br />

the data, and the server response code.<br />

• Document Meta data<br />

The meta data captured by Aria.monitor with regard to the document transferred<br />

<strong>in</strong>cludes the encod<strong>in</strong>g type (e.g. base 64), the byte length of data transferred, the<br />

type of data transferred (e.g. GIF, cgi script), and the body content of the message.<br />

• Cookie Data and user profile data<br />

Cookie data refers to the path taken by a user dur<strong>in</strong>g a prior visit. Aria.monitor<br />

can capture this data so that the server is aware of prior paths and can<br />

automatically customize the users’ <strong>in</strong>teractions based on patterns and preferences<br />

previously exhibited by the user. If the server does not support cookies the<br />

Aria.monitor creates one for the user. In addition, under the control of the<br />

adm<strong>in</strong>istrator the Aria.monitor product can allow user authentication files or other<br />

pseudo-cookie alternatives to be used <strong>in</strong> place of cookies to ma<strong>in</strong>ta<strong>in</strong> the user<br />

profile.<br />

______________________________________________________________________________<br />

The Aria Architecture Page 16 Andromedia, Inc.<br />

White Paper July 1996

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!