
Server behavior techniques 373
This server behavior no longer works correctly because only one parameter is named total.
To solve this problem, make sure that there is a parameter with a unique value and can be
used to match the participants. In the following example, you could make the
total variable
name unique using the column name:
<% itemPrice_total = Recordset1.Fields.Item("itemPrice").¬
Value * 1.0825 %>
<% salePrice_total = Recordset1.Fields.Item("salePrice").¬
Value * 1.0825 %>
<html>
<body>
The total (with taxes) is $<%=itemPrice_total%>
Sale price (with taxes) is $<%=salePrice_total%>
</body>
</html>
The search patterns now uniquely identify and match the participants.
Search pattern resolution
Dreamweaver supports the following actions by using the participant
searchPatterns functionality:
■ File transfer dependency
■ Updating the file paths for any file reference (such as those for include files)
When Dreamweaver creates server models, it builds lists of patterns by scanning all the
participants for special
paramNames attributes. To find URLs to check file dependency and to
fix the pathname, Dreamweaver uses each
searchPattern tag in which one of the
paramNames attribute ends with _url. Multiple URLs can be specified in a single
searchPattern tag.
For each translator
searchPattern tag that has a paramNames attribute value that ends with
_includeUrl, Dreamweaver uses that searchPattern tag to translate include file statements
on the page. Dreamweaver uses a different suffix string to identify include file URLs because
not all URL references are translated. Also, only a single URL can be translated as an include
file.
In resolving a
searchPatterns tag, Dreamweaver uses the following algorithm:
1. Look for the whereToSearch attribute within the searchPatterns tag.
2. If the attribute value starts with tag+, the remaining string is assumed to be the tag name
(no spaces are allowed in the tag name).
Komentarze do niniejszej Instrukcji