URIs for all Personal Tier applications begin with myweb:
, rather than http:
. The Personal Tier APP handler will resolve all URIs that use this custom protocol scheme, whether the URI is to static or dynamic content. For example, an ASP+ application might present the following URIs that are all resolved to local handlers.
myweb://www.microsoft.com/money/default.aspx myweb://www.microsoft.com/money/images/logo.jpg myweb://www.microsoft.com/money/accounts.aspx myweb://www.microsoft.com/money/static/about.htm
The Personal Tier custom protocol scheme for Personal Tier offers a number of benefits. Using the protocol scheme, Personal Tier can intercept requests for local resources and notify the browser that these requests are from a remote location. This helps prevent remote attacks that are looking for a user's private data.
Since Personal Tier starts ASP+ applications and worker processes only when a request originates through the myweb: protocol, there is zero impact on normal Web browsing for users. Browsing will be just as fast, and Personal Tier will not cause the browser to crash.
Remote sites that include Personal Tier and other files can point explicitly to those files stored on the users local computer, thereby allowing load balancing and application portioning between the local computer and the remote site.
See Also
Personal Tier Architecture | URI Mapping and Name Resolution