Author: sebb
Date: Thu Nov 15 15:29:10 2007
New Revision: 595488
URL: http://svn.apache.org/viewvc?rev=595488&view=rev
Log:
Fix up missing anchors
Modified:
jakarta/jmeter/trunk/xdocs/usermanual/boss.xml
jakarta/jmeter/trunk/xdocs/usermanual/index.xml
jakarta/jmeter/trunk/xdocs/usermanual/ldapanswer_xml.xml
jakarta/jmeter/trunk/xdocs/usermanual/ldapops_tutor.xml
jakarta/jmeter/trunk/xdocs/usermanual/regular_expressions.xml
Modified: jakarta/jmeter/trunk/xdocs/usermanual/boss.xml
URL:
http://svn.apache.org/viewvc/jakarta/jmeter/trunk/xdocs/usermanual/boss.xml?rev=595488&r1=595487&r2=595488&view=diff
==============================================================================
--- jakarta/jmeter/trunk/xdocs/usermanual/boss.xml (original)
+++ jakarta/jmeter/trunk/xdocs/usermanual/boss.xml Thu Nov 15 15:29:10 2007
@@ -36,7 +36,7 @@
tools will prove useful. There are a number of products to consider. And
finally,
why is Java a good choice to implement a load-testing/Benchmarking product.
</p>
-<subsection name="§-num;.1 Questions to ask">
+<subsection name="§-num;.1 Questions to ask" anchor="questions">
<p>What is our anticipated average number of users (normal load) ?
</p>
<p>What is our anticipated peak number of users ?
@@ -49,13 +49,13 @@
</p>
<p>What is the testing intended to achieve?</p>
</subsection>
-<subsection name="§-num;.2 Resources">
+<subsection name="§-num;.2 Resources" anchor="resources">
<p>The following resources will prove very helpful. Bear in mind that if you
cannot locate these resources, <b>you</b> will become these resources. As you
already have your work cut out for you, it is worth knowing who the following
people are, so that you can ask them for help if you need it.
</p>
- <subsection name="§-num;.2.1 Network">
+ <subsection name="§-num;.2.1 Network" anchor="network">
<p>Who knows our network topology ? If you run into any firewall or
proxy issues, this will become very important. As well, a private
testing network (which will therefore have very low network latency)
@@ -65,7 +65,7 @@
hardware ?
</p>
</subsection>
- <subsection name="§-num;.2.2 Application">
+ <subsection name="§-num;.2.2 Application" anchor="application">
<p>Who knows how our application functions ? The normal sequence is
<ul>
<li>test (low-volume - can we benchmark our application?)</li>
@@ -82,7 +82,7 @@
</p>
</subsection>
</subsection>
-<subsection name="§-num;.3 What platform should I use to run the
benchmarks/load-tests ?">
+<subsection name="§-num;.3 What platform should I use to run the
benchmarks/load-tests ?" anchor="platform">
<p>This should be a widely-used piece of hardware, with a standard
(i.e. vanilla) software installation. Remember, if you publish your results,
the first thing your clients will do is hire a graduate student to verify them.
@@ -113,20 +113,20 @@
The batch log file can then be loaded into JMeter on a workstation for
analysis, or you can
use CSV output and import the data into a spreadsheet.</p>
</subsection>
-<subsection name="§-num;.4 Tools">
+<subsection name="§-num;.4 Tools" anchor="tools">
<p>The following tools will all prove useful. It is definitely worthwhile to
become familiar with them. This should include trying them out, and reading the
appropriate documentation (man-pages, info-files, application --help messages,
and any supplied documentation).
</p>
- <subsection name="§-num;.4.1 ping">
+ <subsection name="§-num;.4.1 ping" anchor="ping">
<p>
This can be used to establish whether or not you can reach your
target site. Options can be specified so that 'ping' provides the
same type of route reporting as 'traceroute'.
</p>
</subsection>
- <subsection name="§-num;.4.2 nslookup/dig">
+ <subsection name="§-num;.4.2 nslookup/dig" anchor="dig">
<p>
While the <u>user</u> will normally use a human-readable internet
address, <u>you</u> may wish to avoid the overhead of DNS lookups when
@@ -134,7 +134,7 @@
the unique address (dotted quad) of your target site.
</p>
</subsection>
- <subsection name="§-num;.4.3 traceroute">
+ <subsection name="§-num;.4.3 traceroute" anchor="traceroute">
<p>
If you cannot "ping" your target site, this may be used to determine
the problem (possibly a firewall or a proxy). It can also be used
@@ -145,7 +145,7 @@
</p>
</subsection>
</subsection>
-<subsection name="§-num;.5 What other products are there ?">
+<subsection name="§-num;.5 What other products are there ?"
anchor="products">
<p>There are a number of commercial products, which generally have fairly
hefty pricetags. If you can justify it, these are probably the way to go.
If, however, these products do not do exactly what you want, or you are on a
@@ -153,7 +153,7 @@
start by trying the Apache <b>ab</b> tool, as it may very well do the job
if your requirements are not particularly complicated.
</p>
- <subsection name="§-num;.5.1 Apache 'ab' tool">
+ <subsection name="§-num;.5.1 Apache 'ab' tool" anchor="ab">
<p>
You should definitely start with this one. It handles HTTP 'get'
requests
very well, and can be made to handle HTTP 'post' requests with a little
@@ -161,7 +161,7 @@
performance reporting.
</p>
</subsection>
- <subsection name="§-num;.5.2 HttpUnit">
+ <subsection name="§-num;.5.2 HttpUnit" anchor="httpunit">
<p>
This is worth a look. It is a library (and therefore of more interest to
developers) that can be used to perform HTTP tests/benchmarks. It is
@@ -169,14 +169,14 @@
conjunction with <b>JUnit</b>.
</p>
</subsection>
- <subsection name="§-num;.5.3 Microsoft WAS">
+ <subsection name="§-num;.5.3 Microsoft WAS" anchor="WAS">
<p>
This is definitely worth a look. It has an excellent user interface
but it may not do exactly what you want. If this is the case, be aware
that the functionality of this product is not likely to change.
</p>
</subsection>
- <subsection name="§-num;.5.4 JMeter">
+ <subsection name="§-num;.5.4 JMeter" anchor="JMeter">
<p>
If you have non-standard requirements, then this solution offers an
open-source community to provide them (of course, if you are reading
@@ -185,7 +185,7 @@
</p>
</subsection>
</subsection>
-<subsection name="§-num;.6 Why Java ?">
+<subsection name="§-num;.6 Why Java ?" anchor="java">
<p>Why not Perl or C ?
</p>
<p>Well, Perl might be a very good choice except that the Benchmark package
Modified: jakarta/jmeter/trunk/xdocs/usermanual/index.xml
URL:
http://svn.apache.org/viewvc/jakarta/jmeter/trunk/xdocs/usermanual/index.xml?rev=595488&r1=595487&r2=595488&view=diff
==============================================================================
--- jakarta/jmeter/trunk/xdocs/usermanual/index.xml (original)
+++ jakarta/jmeter/trunk/xdocs/usermanual/index.xml Thu Nov 15 15:29:10 2007
@@ -21,12 +21,12 @@
</properties>
<body>
-<section name="User's Manual">
+<section name="User's Manual" anchor="index">
<p>Click on the section name to go straight to the section.
Click on the "+" to go to the relevant section of the detailed section
list,
where you can select individual subsections.</p>
-<subsection name="Section Summary">
+<subsection name="Section Summary" anchor="summary">
<ul>
<li><a href="#intro">+</a>...<a href="intro.html">1. Introduction</a></li>
<li><a href="#get-started">+</a>...<a href="get-started.html">2. Getting
Started</a></li>
@@ -52,7 +52,7 @@
<li><a href="#glossary">+</a>...<a href="glossary.html">21. Glossary</a></li>
</ul>
</subsection>
-<subsection name="Detailed Section List">
+<subsection name="Detailed Section List" anchor="details">
<ul>
<li><a name="intro"/><a href="intro.html">1. Introduction</a></li>
<ul>
Modified: jakarta/jmeter/trunk/xdocs/usermanual/ldapanswer_xml.xml
URL:
http://svn.apache.org/viewvc/jakarta/jmeter/trunk/xdocs/usermanual/ldapanswer_xml.xml?rev=595488&r1=595487&r2=595488&view=diff
==============================================================================
--- jakarta/jmeter/trunk/xdocs/usermanual/ldapanswer_xml.xml (original)
+++ jakarta/jmeter/trunk/xdocs/usermanual/ldapanswer_xml.xml Thu Nov 15
15:29:10 2007
@@ -30,7 +30,7 @@
construct an answer in xml encoding, so the results may be parsed with
regextracter or alike functions.
</p>
-<subsection name="1 Global overview">
+<subsection name="1 Global overview" anchor="overview">
<p>
The global structure is as follows:<br/>
<!--
@@ -48,7 +48,7 @@
</ol>
-->
</p>
-<subsection name="1.1 The operation section">
+<subsection name="1.1 The operation section" anchor="operation">
<p>
The operation section defines the operation as it is sent to the LDAP Server.
The
following tags (with a short explanation) are used
@@ -147,7 +147,7 @@
</p>
</subsection>
-<subsection name="1.2 respons message section">
+<subsection name="1.2 Response message section" anchor="response_message">
<p>
As the response code, the official LDAP error definitions are used, so this
section
contains the error message as returned from the server.
@@ -157,7 +157,7 @@
<responsemessage><br>
--></p>
</subsection>
-<subsection name="1.3 Responsecode section">
+<subsection name="1.3 Response code section" anchor="response_code">
<p>
As the response code, the official LDAP error definitions are used, so this
section
contains the error number as returned from the server.
@@ -168,7 +168,7 @@
-->
</p>
</subsection>
-<subsection name="1.4 Search Result section">
+<subsection name="1.4 Search Result section" anchor="search">
<p>
The following tag is used:
<!--
Modified: jakarta/jmeter/trunk/xdocs/usermanual/ldapops_tutor.xml
URL:
http://svn.apache.org/viewvc/jakarta/jmeter/trunk/xdocs/usermanual/ldapops_tutor.xml?rev=595488&r1=595487&r2=595488&view=diff
==============================================================================
--- jakarta/jmeter/trunk/xdocs/usermanual/ldapops_tutor.xml (original)
+++ jakarta/jmeter/trunk/xdocs/usermanual/ldapops_tutor.xml Thu Nov 15 15:29:10
2007
@@ -37,19 +37,19 @@
The type of an
object is determined by the "structural objectClass" eg person,
organizationalUnit or country.<br/>
The attributes
contain the data of an object, eg mailadress, name, streetadress etc. Each
attribute can have 0, 1 or more values.
</p>
-<subsection name="1 Bind operation">
+<subsection name="1 Bind operation" anchor="bind">
<p>
Any contact with an
LDAP server MUST start with a bind request. LDAP is a state dependent protocol.
Without opening a session to
a LDAP server, no
additional request can be made.
Due to some
peculiarities in the JAVA libraries, 2 different bind operations are
implemented.
</p>
-<subsection name="1.1 Thread Bind">
+<subsection name="1.1 Thread Bind" anchor="thread_bind">
<p>
This bind is
meant to open a session to a LDAP server. Any testplan should use this
operation as the starting point from a session.
For each Thread
(each virtual user) a seperate connection with the LDAP server is build, and so
a seperate Thread bind is performed.
</p>
</subsection>
-<subsection name="1.2 Single bind/unbind">
+<subsection name="1.2 Single bind/unbind" anchor="single">
<p >
This bind is
used for user authentication verification.
A proper
developed LDAP client, who needs an authenticated user, perform a bind with a
given distinguished name and password.
@@ -58,34 +58,34 @@
</p>
</subsection>
</subsection>
-<subsection name="2 Unbind">
+<subsection name="2 Unbind" anchor="unbind">
<p>
To close a
connection to a LDAP server, an unbind operation is needed.
As the Single
bind/unbind operation already (implicitly) performs an unbind, only a Thread
unbind operation is needed.
This Thread
unbind just closes the connection and cleans up any resources it has used.
</p>
</subsection>
-<subsection name="3 Compare">
+<subsection name="3 Compare" anchor="compare">
<p>
The compare operation needs the
full distinguished name from a LDAP object, as well as a attribute and a value
for the attribute.
It will simply check: "Has this
object really this attribute with this value?".
Typical use is checking the
membership of a certain user with a given group.
</p>
</subsection>
-<subsection name="4 Search">
+<subsection name="4 Search" anchor="search">
<p>
The search test
simply searches for all objects which comply with a given search filter, eg.
all persons
with a "employeeType=inactive" or "all persons with a userID equals user1"
</p>
</subsection>
-<subsection name="5 Add">
+<subsection name="5 Add" anchor="add">
<p>
This simply add
an object to the LDAP directory.
Off course the
combination of attributes and distinguishedName must be valid!
</p>
</subsection>
-<subsection name="6 Modify">
+<subsection name="6 Modify" anchor="modify">
<p>
This operation
modifies one or more attributes from a given object.
It needs the
distinghised name from the object, as well as the attributes and the new values
for this attribute.<br/>
@@ -94,13 +94,13 @@
delete, to
delete a value form an attribute, or to delete all the values of an
attribute<br/>
</p>
</subsection>
-<subsection name="7 Delete">
+<subsection name="7 Delete" anchor="delete">
<p>
This operation
deletes an object from the LDAP server.
It needs the
distinghised name from the object.
</p>
</subsection>
-<subsection name="8 modDN">
+<subsection name="8 modDN" anchor="moddn">
<p>
This operation
modifies the distinguished name from an object (it "moves" the object).<br/>
It comes in two
flavours, just renaming an entry, then you specify a new RDN (relative
distinguished name, this is the lowest part of the DN)<br/>
Modified: jakarta/jmeter/trunk/xdocs/usermanual/regular_expressions.xml
URL:
http://svn.apache.org/viewvc/jakarta/jmeter/trunk/xdocs/usermanual/regular_expressions.xml?rev=595488&r1=595487&r2=595488&view=diff
==============================================================================
--- jakarta/jmeter/trunk/xdocs/usermanual/regular_expressions.xml (original)
+++ jakarta/jmeter/trunk/xdocs/usermanual/regular_expressions.xml Thu Nov 15
15:29:10 2007
@@ -28,7 +28,7 @@
<body>
<section name="§-num;. Regular Expressions" anchor="regex">
-<subsection name="§-num;.1 Overview">
+<subsection name="§-num;.1 Overview" anchor="overview">
<p>
JMeter includes the pattern matching software <a
href="http://jakarta.apache.org/oro/";>Apache Jakarta ORO</a>
<br/>
@@ -70,7 +70,7 @@
The solution is to use Perl5 extended regular expressions, i.e. /abc/i becomes
(?i)abc
</p>
</subsection>
-<subsection name="§-num;.2 Examples">
+<subsection name="§-num;.2 Examples" anchor="examples">
<p>
Extract single string
<br/>
@@ -125,7 +125,7 @@
These variables can be referred to later on in the JMeter test plan, as
${MYREF}, ${MYREF_g1} etc
</p>
</subsection>
-<subsection name="§-num;.3 Line mode">
+<subsection name="§-num;.3 Line mode" anchor="line_mode">
<p>The pattern matching behave in various slightly different ways,
depending on the setting of the multi-line and single-line modifiers.
</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
