o
p
q
r
s
t
u
v
u
w
x
y
x
z
{
|
{
y
}
x
~
{
r
t
u
u
|
{
w
x
y
x
z
{
|
{
y
s
p
s
p
p
s
s
A
A
A
A
A
A
AE
A
A
A
A
C
E
E
A
E
A
E
A
A
A
I
I
I
I
N
O
O
I
O
O
O
O
O
I
N
O
O
O
O
O
U
U
U
U
A
C
AE
Y
A
A
For any service there will usually be multiple mappings like the one described previously.
The complete DTD for a SLA is given in Appendix A.
4.5.2 Parameter Definition
The ability to derive parameters from the base parameters logged for each request was
described in the Chapter 3. It was decided that for flexibility, the queries that calculated the
derived parameters should be defined using XML and then stored in the local database. This
has the advantage of making the framework flexible in that it is possible to define new
parameters without having to modify the source code of the framework.
4.5.3 Database Design
A number of components in the HTTPQoS filter make use of an Oracle Lite database to
store and retrieve data. This includes the storage of data collected for HTTP requests and
responses, SLAs that are downloaded from the SLAVSP and data on how to calculate
derived parameters described previously.
"