1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
|
<HTML><HEAD>
<TITLE>Tcl API Reference -- ns_register_trace</TITLE>
<LINK rel=Previous href="tapi-104.htm">
<LINK rel=ToC href="toc.htm">
<LINK rel=Index href="master.htm">
<LINK rel=Next href="tapi-106.htm">
</HEAD><BODY BGCOLOR="#ffffff"><A NAME="topofpage"></A>
<TABLE WIDTH=100%>
<TR>
<TD ALIGN=LEFT>
<A NAME="topofpage"></A> <IMG SRC="as-c-sm.gif">
</TD>
<TD ALIGN=RIGHT>
<A href="tapi-104.htm"><IMG BORDER="0" src=navbprev.gif alt="[ Previous ]"></A>
<A href=toc.htm> <IMG BORDER="0" src=navbhome.gif alt="[ Contents ]"></A>
<A href=master.htm> <IMG BORDER="0" src=navbhelp.gif alt="[ Index ]"></A>
<A href="tapi-106.htm"> <IMG BORDER="0" src=navbnext.gif alt="[ Next ]"></A>
<A name="7983"> </A>
</TD>
</TR>
</TABLE>
<a name="81668">
</a><h3>ns_register_trace</h3>
<a name="81669">
</a><h4>Overview</h4>
<p><a name="81670">
</a>Register a Tcl trace script to a method and matching URL</p>
<p><a name="148669">
</a>(Note: This function is obsolete. Use <b>ns_register_filter</b> instead.)</p>
<a name="81671">
</a><h4>Syntax</h4>
<p><a name="81672">
</a><b>ns_register_trace</b> <i>method URLpattern script</i> ?<i>args</i>?</p>
<a name="81673">
</a><h4>Description</h4>
<p><a name="81674">
</a><b>ns_register_trace</b> registers a Tcl script as a trace for the specified method/URL combination. After the server handles the request for the specified <i>method</i> on an URL that matches the <i>URLpattern</i>, it calls the trace <i>script</i> with the connection id and any arguments (<i>args</i>) specified.</p>
<p><a name="81675">
</a>The <i>URLpattern</i> can contain standard string-matching characters. For example, these are valid <i>URLpattern</i>s:</p>
<pre> <a name="81676"></a>/employees/*.tcl
<a name="81677"></a>/accounts/*/out
</pre><p><a name="81678">
</a><h4>Note</h4>
<p><a name="81679">
</a><b>ns_register_trace</b> is similar to <b>ns_register_proc</b> except that the pattern-matching for the URL is performed differently. With <b>ns_register_proc</b>, the specified URL is used to match that URL and any URL below it in the hierarchy. Wildcards such as "*" are meaningful only for the final part of the URL, such as <code>/scripts/*.tcl</code>. With <b>ns_register_trace</b>, the <i>URLpattern</i> is used to match URLs as a string with standard string-matching characters. </p>
<p><a name="86801">
</a><b>ns_register_proc</b> results in a single match, whereas multiple <b>ns_register_trace</b>'s can be matched and will be called.</p>
<TABLE BORDER="2" CELLPADDING="1" width="100%">
<TR><TD COLSPAN=3><P ALIGN=Center>
<IMG SRC="bluebult.gif">
<A HREF="#topofpage">
<FONT SIZE=-1>Top of Page</FONT></A>
<IMG SRC="bluebult.gif">
</TD></TR>
<TR><TD COLSPAN=3><P ALIGN=Center>
<A href="tapi-104.htm">
<IMG BORDER="0" src=navbprev.gif alt="[ Previous ]"></A>
<A href=toc.htm>
<IMG BORDER="0" src=navbhome.gif alt="[ Contents ]"></A>
<A href=master.htm>
<IMG BORDER="0" src=navbhelp.gif alt="[ Index ]"></A>
<A href="tapi-106.htm">
<IMG BORDER="0" src=navbnext.gif alt="[ Next ]"></A>
<BR align=center>
<FONT size=-1>Copyright © 1998-99 America Online,
Inc.</FONT>
</TD></TR></TABLE></BODY></HTML>
|
