Classe: TUrlMapping  - X-Ref

TUrlMapping Class

The TUrlMapping module allows aributary URL path to be mapped to a
particular service and page class. This module must be configured
before a service is initialized, thus this module should be configured
globally in the <tt>application.xml</tt> file and before any services.
<code>
<module id="friendly-url" class="System.Web.TUrlMapping">
<url ServiceParameter="Posts.ViewPost" pattern="post/{id}/?" parameters.id="\d+" />
<url ServiceParameter="Posts.ListPost" pattern="archive/{time}/?" parameters.time="\d{6}" />
<url ServiceParameter="Posts.ListPost" pattern="category/{cat}/?" parameters.cat="\d+" />
</module>
<module id="request" class="THttpRequest" UrlManager="friendly-url" />
</code>

See {@link TUrlMappingPattern} for details regarding the mapping patterns.
Similar to other modules, the <tt>&lt;url /&gt;</tt> configuration class
can be customised using the <tt>class</tt> property.

The URL mapping are evaluated in order, only the first mapping that matches
the URL will be used. Cascaded mapping can be achieved by placing the URL mappings
in particular order. For example, placing the most specific mappings first.

The mapping can be load from an external file by specifying a configuration
file using the {@link setConfigFile ConfigFile} property.

Since TUrlMapping is a URL manager extending from {@link TUrlManager},
you may override {@link TUrlManager::constructUrl} to support your pattern-based
URL scheme.

Classe: TUrlMappingPattern  - X-Ref

URL Mapping Pattern Class

Describes an URL mapping pattern, if a given URL matches the pattern, the
TUrlMapping class will alter the THttpRequest parameters. The
url matching is done using patterns and regular expressions.

The {@link setPattern Pattern} property takes an string expression with
parameter names enclosed between a left brace '{' and a right brace '}'.
The pattens for each parameter can be set using {@link getParameters Parameters}
attribute collection. For example
<code>
<url ... pattern="articles/{year}/{month}/{day}"
parameters.year="\d{4}" parameters.month="\d{2}" parameters.day="\d+" />
</code>

In the above example, the pattern contains 3 parameters named "year",
"month" and "day". The pattern for these parameters are, respectively,
"\d{4}" (4 digits), "\d{2}" (2 digits) and "\d+" (1 or more digits).
Essentially, the <tt>Parameters</tt> attribute name and values are used
as substrings in replacing the placeholders in the <tt>Pattern</tt> string
to form a complete regular expression string. A full regular expression
may be expressed using the <tt>RegularExpression</tt> attribute or
as the body content of the &lt;module&gt; tag. The above pattern is equivalent
to the following regular expression pattern.
<code>
/articles\/(?P<year>\d{4})\/(?P<month>\d{2})\/(?P<day>\d+)/u
</code>
The above regular expression used the "named group" feature available in PHP.
Notice that you need to escape the slash in regular expressions.

In the TUrlMappingPattern class, the pattern is matched against the
<b>path</b> property of the url only.

Thus, only an url that matches the pattern will be valid. For example,
an url "<tt>http://example.com/articles/2006/07/21</tt>" will matches and is valid.
However, "<tt>http://example.com/articles/2006/07/hello</tt>" is not
valid since the "day" parameter pattern is not satisfied.

The parameter values are available through the standard <tt>Request</tt>
object. For example, <tt>$this->Request['year']</tt>.

The {@link setServiceParameter ServiceParameter} and {@link setServiceID ServiceID}
(the default ID is 'page') set the service parameter and service id respectively.
The service parameter for the TPageService is the Page class name, other service
may use the service parameter differently.

For more complicated mappings, the body of the <tt>&lt;url&gt;</tt>
can be used to specify the mapping pattern.