Sign up to receive free email alerts when patent applications with chosen keywords are publishedSIGN UP

Abstract:

A system, method and computer-readable medium for client-side processing
of resource identifiers. A client request for content is returned that
includes information for generating a request for translation information
and a number of embedded resource identifiers. Based on the information
for generating a request for translation information, the client
generates and obtains translation information and processes the embedded
resource identifiers to obtain resources from a service provider.

Claims:

1. A computer-implemented method comprising: obtaining, by a service
provider, a request for resource identifier processing information,
wherein the request for the resource identifier processing information is
generated by a client computer based on execution of code included in
information responsive to a previous content request; transmitting, by
the service provider, responsive processing information, wherein the
responsive processing information includes information for identifying a
service provider resource for providing requested content; and obtaining,
by the service provider, a request for content corresponding to
translated original content identifiers, wherein the translated original
content identifiers are translated by the client computer utilizing at
least in part the responsive processing information.

2. The method as recited in claim 1, wherein the information for
identifying the service provider corresponds to a uniform resource
locator of the service provider.

3. The method as recited in claim 1, wherein the information for
identifying the service provider includes a domain name of the service
provider.

4. The method as recited in claim 1, wherein the information responsive
to the previous content request includes original content identifiers and
wherein the original content identifiers correspond to uniform resource
locators of a content provider.

5. The method as recited in claim 1, wherein the information responsive
to the previous content request includes original content identifiers and
wherein the original content identifiers correspond to uniform resource
locators of a service provider.

6. The method as recited in claim 1, wherein the request for content
corresponding to translated original content identifiers does not require
a DNS server providing the translated original content identifiers.

7. The method as recited in claim 1, further comprising transmitting, by
the service provider, one or more original content identifiers.

8. A computer-implemented method comprising: providing, by a service
provider, executable code for causing a client computing device to
generate a request to the service provider for translation information;
providing, by a service provider, at least one original URL; obtaining,
by the service provider, a request for translation information, wherein
the request for translation information is generated by the client
computing device through the execution of the provided executable code;
determining, by the service provider, identification information of a
source corresponding to the service provider for obtaining requested
content; transmitting, by the service provider, responsive translation
information for causing translation of the at least one original URL,
wherein the responsive translation information includes the determined
identification information; and obtaining, by the service provider, a
request for content corresponding to translated URLs including at least
in part the determined identification information, wherein the request
for content is generated by the client computing device.

9. The method as recited in claim 8, wherein the request for content
corresponding to translated URLs does not require a DNS server providing
the translated URLs.

10. A system comprising: at least one computing device corresponding to a
service provider, the at least one computing device operative to: obtain
a request for resource identifier processing information, wherein the
request for the resource identifier processing information is generated
by a client computer based on execution of code included in information
responsive to a previous content request; transmit responsive processing
information, wherein the responsive processing information includes
information for identifying a service provider resource for providing
requested content; and obtain a request for content corresponding to
translated original content identifiers, wherein the translated original
content identifiers are translated by the client computer utilizing at
least in part the responsive processing information.

11. The system as recited in claim 10, the information for identifying
the service provider corresponds to a uniform resource locator of the
service provider.

12. The system as recited in claim 10, wherein the information for
identifying the service provider includes a domain name of the service
provider.

13. The system as recited in claim 10, wherein the information responsive
to the previous content request includes original content identifiers and
wherein the original content identifiers correspond to uniform resource
locators of a content provider.

14. The system as recited in claim 10, wherein the information responsive
to the previous content request includes original content identifiers and
wherein the original content identifiers correspond to uniform resource
locators of a service provider.

15. The system as recited in claim 10, wherein the request for content
corresponding to translated original content identifiers does not require
a DNS server providing the translated original content identifiers.

16. The system as recited in claim 10, wherein the at least one computing
device is further operative to transmit one or more original content
identifiers.

17. The system as recited in claim 10, wherein the at least one computing
device is further operative to provide the executable code for causing
the client computer to generate a request for translation information,
wherein the executive code is provided to a content provider for
embedding in a network resource.

18. The system as recited in claim 18 further comprising memory for
storing the executable code for causing the client computer to generate a
request for resource identifier processing information.

19. A system comprising: at least one computing device corresponding to a
service provider, the at least one computing device operative to: provide
executable code for causing a client computing device to generate a
request to the service provider for translation information; provide at
least one original URL; obtain a request for translation information,
wherein the request for translation information is generated by the
client computing device through the execution of the provided executable
code; determine identification information of a source corresponding to
the service provider for obtaining requested content; transmit responsive
translation information for causing translation of the at least one
original URL, wherein the responsive translation information includes the
determined identification information; and obtain a request for content
corresponding to translated URLs including at least in part the
determined identification information, wherein the request for content is
generated by the client computing device.

20. The system as recited in claim 19, wherein the request for content
corresponding to translated URLs does not require a DNS server providing
the translated URLs.

Description:

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is a divisional of U.S. patent application Ser.
No. 12/060,013, entitled "NETWORK RESOURCE IDENTIFICATION," and filed
Mar. 31, 2008, the disclosure of which is incorporated herein by
reference.

BACKGROUND

[0002] Generally described, computing devices and communication networks
can be utilized to exchange information. In a common application, a
computing device can request content from another computing device via
the communication network. For example, a user at a personal computing
device can utilize a software browser application to request a Web page
from a server computing device via the Internet. In such embodiments, the
user computing device can be referred to as a client computing device and
the server computing device can be referred to as a content provider.

[0003] Content providers are generally motivated to provide requested
content to client computing devices often with consideration of efficient
transmission of the requested content to the client computing device
and/or consideration of a cost associated with the transmission of the
content. For larger scale implementations, a content provider may receive
content requests from a high volume of client computing devices which can
place a strain on the content provider's computing resources.
Additionally, the content requested by the client computing devices may
have a number of components, which can further place additional strain on
the content provider's computing resources.

[0004] With reference to an illustrative example, a requested Web page, or
original content, may be associated with a number of additional
resources, such as images or videos, that are to be displayed with the
Web page. In one specific embodiment, the additional resources of the Web
page are identified by a number of embedded resource identifiers, such as
uniform resource locators ("URLs"). In turn, software on the client
computing devices typically processes embedded resource identifiers to
generate requests for the content. Often, the resource identifiers
associated with the embedded resources reference a computing device
associated with the content provider such that the client computing
device would transmit the request for the additional resources to the
referenced content provider computing device. Accordingly, in order to
satisfy a content request, the content provider would provide client
computing devices data associated with the Web page as well as the data
associated with the embedded resources.

[0005] Some content providers attempt to facilitate the delivery of
requested content, such as Web pages and/or resources identified in Web
pages, through the utilization of a content delivery network ("CDN")
service provider. A CDN service provider typically maintains a number of
computing devices in a communication network that can maintain content
from various content providers. In turn, content providers can instruct,
or otherwise suggest to, client computing devices to request some, or
all, of the content provider's content from the CDN service provider's
computing devices.

[0006] With reference to the previous illustrative example, the content
provider can leverage a CDN service provider with the modification or
substitution of resource identifiers associated with the embedded
resources. Specifically, the resource identifiers can reference a
computing device associated with the CDN service provider such that the
client computing device would transmit the request for the additional
resources to the referenced CDN service provider computing device.
Typically, the content provider facilitates the utilization of a CDN
service provider by including CDN-provider specific resource identifiers
in requested content (e.g., Web pages). This approach generally
corresponds to an "offline" process implemented by the content provider
in advance of receipt of a request for the original content from the
client computing devices. Accordingly, modifications to resource
identifiers, such as to provide alternative resource identifiers for the
same CDN service provider, to provide additional information utilized by
CDN service providers in processing the request for content and/or to
identify alternative CDN service providers, can become inefficient as
they typically require implementation of the offline process of the
content provider.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The foregoing aspects and many of the attendant advantages of this
invention will become more readily appreciated as the same become better
understood by reference to the following detailed description, when taken
in conjunction with the accompanying drawings, wherein:

[0008] FIG. 1 is a block diagram illustrative of a content delivery
environment including a number of client computing devices, content
provider, and a content delivery network service provider;

[0009] FIG. 2 is a block diagram of the content delivery environment of
FIG. 1 illustrating the registration of a content provider with a content
delivery service provider;

[0010] FIG. 3 is a block diagram of the content delivery environment of
FIG. 1 illustrating the generation and processing of a content request
from a client computing device to a content provider;

[0011]FIG. 4 is a block diagram of the content delivery environment of
FIG. 1 illustrating the generation and processing of a translation
information request from a client computing device to a content delivery
network service provider;

[0012]FIG. 5 is a block diagram of the content delivery environment of
FIG. 1 illustrating the generation and processing of embedded resource
requests from a client computing device to a content delivery network
service provider;

[0013] FIG. 6 is a block diagram of the content delivery environment of
FIG. 1 illustrating the generation and processing of a subsequent content
request from a client computing device to a content provider;

[0014]FIG. 7 is a block diagram of the content delivery environment of
FIG. 1 illustrating the generation and processing of embedded resource
requests from a client computing device to a content delivery network
service provider; and

[0015] FIG. 8 is a flow diagram illustrative of a resource identifier
processing routine implemented by a client computing device to process
embedded resource identifiers with translation information provided by a
content delivery network service provider.

DETAILED DESCRIPTION

[0016] Generally described, the present disclosure is directed to the
management of resource identifiers utilized by a client computing device
to request content from a network resource, such as content delivery
network ("CDN") service providers. Specifically, aspects of the
disclosure will be described with regard to the processing, by a client
computing device, of original resource identifiers associated with
embedded resources with translation information provided by a CDN service
provider. Although various aspects of the disclosure will be described
with regard to illustrative examples and embodiments, one skilled in the
art will appreciate that the disclosed embodiments and examples should
not be construed as limiting.

[0017] FIG. 1 is a block diagram illustrative of content delivery
environment 100 for the management of resource identifiers. As
illustrated in FIG. 1, the content delivery environment 100 includes a
number of client computing devices 102 (generally referred to as clients)
for requesting content from a content provider and/or a CDN service
provider. In an illustrative embodiment, the client computing devices 102
can correspond to a wide variety of computing devices including personal
computing devices, laptop computing devices, hand-held computing devices,
terminal computing devices, mobile devices, wireless devices, various
electronic devices and appliances and the like. In an illustrative
embodiment, the client computing devices 102 include necessary hardware
and software components for establishing communications over a
communication network 108, such as a wide area network or local area
network. For example, the client computing devices 102 may be equipped
with networking equipment and browser software applications that
facilitate communications via the Internet or an intranet.

[0018] Additionally, the client computing devices 102 may also include
necessary hardware and software components to execute, or otherwise
process, translation information as will be described in greater detail
below. One skilled in the relevant art will appreciate the additional
hardware/software components for processing the translation information
that may be included with the execution of a multi-purpose software
application, such as a browser software application. Alternatively, some
or all of the additional hardware/software components may be embodied in
stand alone or specialized components configured for the processing of
the translation information.

[0019] The content delivery environment 100 can also include a content
provider 104 in communication with the one or more client computing
devices 102 via the communication network 108. The content provider 104
illustrated in FIG. 1 corresponds to a logical association of one or more
computing devices associated with a content provider. Specifically, the
content provider 104 can include a web server component 110 corresponding
to one or more server computing devices for obtaining and processing
requests for content (such as Web pages) from the client computing
devices 102. The content provider 104 can further include an origin
server component 112 and associated storage component 114 corresponding
to one or more computing devices for obtaining and processing requests
for network resources from the CDN service provider. One skilled in the
relevant art will appreciate that the content provider 104 can be
associated with various additional computing resources, such additional
computing devices for administration of content and resources, DNS name
servers, and the like.

[0020] With continued reference to FIG. 1, the content delivery
environment 100 can further include a CDN service provider 106 in
communication with the one or more client computing devices 102 and the
content providers 104 via the communication network 108. The CDN service
provider 106 illustrated in FIG. 1 corresponds to a logical association
of one or more computing devices associated with a CDN service provider.
Specifically, the CDN service provider 106 can include a number of Point
of Presence (POP) locations 116, 122, 128 that correspond to nodes on the
communication network 108. Each POP 116, 122, 128 includes a DNS
component 118, 124, 130 made up of a number of DNS server computing
devices for resolving DNS queries from the client computers 102. Each POP
116, 122, 128 also includes a resource cache component 120, 126, 132 made
up of a number of cache server computing devices for storing resources
from content providers and transmitting various requested resources to
various client computers.

[0021] In an illustrative embodiment, the DNS component 118, 124, 130 and
resource cache component 120, 126, 132 are considered to be logically
grouped, regardless of whether the components, or portions of the
components, are physically separate. Additionally, although the POPs 116,
122, 128 are illustrated in FIG. 1 as logically associated with the CDN
service provider 106, the POPs will be geographically distributed
throughout the communication network 108 in a manner to best serve
various demographics of client computing devices 102. Additionally, one
skilled in the relevant art will appreciate that the CDN service provider
106 can be associated with various additional computing resources, such
additional computing devices for administration of content and resources,
and the like.

[0022] Although not illustrated in FIG. 1, each client computing device
102 utilizes some type of local DNS resolver component, such as a DNS
Name server, that generates the DNS queries attributed to the client
computer. In one embodiment, the local DNS resolver component may belong
to an enterprise network to which the client computer belongs. In another
embodiment, the local DNS resolver component may belong to an Internet
Service Provider (ISP) that provides the network connection to the client
computer.

[0023] With reference now to FIG. 2-7, the interaction between various
components of the content delivery environment 100 of FIG. 1 will be
illustrated. For purposes of the example, however, the illustration has
been simplified such that many of the components utilized to facilitate
communications are not shown. One skilled in the relevant art will
appreciate that such components can be utilized and that additional
interactions would accordingly occur without departing from the spirit
and scope of the present disclosure.

[0024] With reference to FIG. 2, an illustrative interaction for
registration of a content provider 104 with the CDN service provider 106
will be described. As illustrated in FIG. 2, the CDN content registration
process begins with registration of the content provider 104 with the CDN
service provider 106. In an illustrative embodiment, the content provider
104 utilizes a registration application program interface ("API") to
register with the CDN service provider 106 such that the CDN service
provider 106 can provide content on behalf of the content provider 104.
The registration API includes the identification of the origin server 112
of the content provider 104 that will provide requested resources to the
CDN service provider 106.

[0025] One skilled in the relevant art will appreciate that upon
identification of appropriate origin servers 112, the content provider
104 can begin to direct requests for content from client computing
devices 102 to the CDN service provider 106. Specifically, in accordance
with DNS routing principles, a client computing device request
corresponding to a resource identifier would eventually be directed
toward a POP 116, 122, 128 associated with the CDN service provider 106.
In the event that the resource cache component 120, 126, 132 of a
selected POP does not have a copy of a resource requested by a client
computing device 102, the resource cache component will request the
resource from the origin server 112 previously registered by the content
provider 104.

[0026] With continued reference to FIG. 2, upon receiving the registration
API, the CDN service provider 106 obtains the registration information
and generates, or otherwise obtains, translation request code. In an
illustrative embodiment, and as will be explained in greater detail
below, the translation request code corresponds to data or instructions
that are processed by the client computing devices 102 to cause the
client computing devices 102 to request translation information from the
CDN service provider 106. In an illustrative embodiment, the translation
request code can correspond to script-based instructions that are
processed by a browser software application on the client computing
device 102 that causes the browser software application to request the
translation information from the CDN service provider 106. One skilled in
the relevant art will appreciate, however, that the translation request
code can be embodied in any one of a variety of executable code formats.

[0027] The CDN service provider 106 returns the translation request code
to the content provider 104 along with any additional information. In
turn, the content provider 104 can then store for the translation request
code for embedding in requested content or otherwise embed (or associate)
the translation request code with requested content (such as Web page
markup language). In an illustrative embodiment, the translation request
code can be applicable to multiple content providers 104. Alternatively,
the translation request code can be unique to each particular content
provider 104. Still further, the CDN service provider 106 may provide
additional logic to the content providers 104 that controls the
circumstances and/or methodologies for embedding the translation request
code into content. For example, the translation request code can include
instructions (or executable code) that defines that the type of content
(e.g., specific Web pages) for which the translation request code will
apply.

[0028] With reference now to FIG. 3, after completion of the registration
and embedding processes illustrated in FIG. 2, a client computing device
102 generates a content request that is received and processed by the
content provider 104, such as through the Web server 110. In accordance
with an illustrative embodiment, the request for content can be in
accordance with common network protocols, such as the hypertext transfer
protocol ("HTTP"). Upon receipt of the content request, the content
provider identifies the appropriate responsive content. In an
illustrative embodiment, the requested content can correspond to a Web
page that is displayed on the client computing device 102 via the
processing of information, such as hypertext markup language ("HTML"),
extensible markup language ("XML"), and the like. The requested content
can also include a number of embedded resource identifiers that
corresponds to resource objects that should be obtained by the client
computing device 102 as part of the processing of the requested content.
Additionally, the requested content will also include the embedded
translation execution code previously provided by the CDN service
provider 106. In an illustrative embodiment, the embedded execution code
can be arranged in a manner such that it is processed prior to processing
any other of the content in the requested content or processed in the
earlier stages of the processing of the requested content, as allowed.
Alternatively, the embedded execution code can also be arranged such that
it can be parsed by the client computing device 102 from the other
requested content.

[0029] Generally, the identification of the resources provided by the
content provider 104 will be in the form of a resource identifier that
can be processed by the client computing device 102, such as through a
browser software application. In an illustrative embodiment, the resource
identifiers can be in the form of a uniform resource locator ("URL").
Because the resource identifiers are included in the requested content
directed to the content provided, the resource identifiers can be
referred to generally as the "original URL." For purposes of an
illustrative example, the original URL can identify a domain of the
content provider 104 (e.g., contentprovider.com), a name of the resource
to be requested (e.g., "resource.xxx") and a path where the resource will
be found (e.g., "path"). In this illustrative example, the original URL
has the form of:

http://www.contentprovider.com/path/resource.xxx

[0030] With reference now to FIG. 4, upon receipt of the requested
content, including the embedded resource identifiers and the translation
request code, the client computing device 102 processes the translation
request code in a manner that causes the client computing device 102 to
request translation information from the CDN service provider 106. As
described above, the translation request code can include script-based
instructions and information that instructs a browser software
application on the client computing device 102 to generate the request
for translation information. The translation information request can
include information identifying the content provider 104, the specific
client computing device 102, the type/size of requested content (e.g.
large image files), and additional information that could be used by the
CDN service provider 106 to determine an appropriate POP for providing
requested content. For example, the request for translation information
can include network topology and/or network performance information
accumulated by the client computing device 102 or measured during the
transmission of the request. Still further, some of the information may
be inferentially obtained by the CDN service provider 106. For example, a
client computing device 102 geographic location may be inferred from an
Internet Protocol ("IP") address associated with the client computing
device.

[0031] As illustrated in FIG. 4, the translation information request can
be directed to a specific POP, such as POP 116, provided by the CDN
service provider 106. In one embodiment, the translation request code can
include a listing of one or more specific network addresses, such as IP
addresses, on POPs that can process the request for translation
information. In another embodiment, the translation request code can
include a single network address shared by one or more POPs such that a
request for the translation information utilizes a one-to-many network
routing schema, such as anycast, such a specific POP will receive the
request as a function of network topology. In both this embodiment and
the previous embodiment, the network address may correspond to a
particular computing device in the POP or may correspond generally to the
POP. Still further, in an alternative embodiment, the CDN service
provider 106 may maintain a computing device separate from a POP for
processing translation information requests from client computing devices
102.

[0032] Upon receipt of the translation information request, the CDN
service provider 106, such as through POP 116, generates translation
information that will be used to process the original URLs associated
with the embedded objects. In an illustrative embodiment, translation
information corresponds to information that will be used to modify the
URL for subsequent processing by the CDN service provider 106. Such
information will include the identification of one or more domain names
associated with the CDN service provider 106 that will cause the request
for content to be resolved to the CDN service provider 106 and not the
content provider 104. The translation information can also include
additional processing information that allows the CDN service provider
106 to select which POP, resource cache component or specific cache
server computing device will provide requested content. For example, the
translation information can include information identifying the specific
content provider, a particular regional coverage plan associated with the
content provider 104, service level plans associated with the content
provider 104, a geographic location/region associated with the client
computing device 102, and the like.

[0033] In another embodiment, the translation information can include the
identification of specific network addresses of the cache server
components that will process the resource request from the client
computing device 102. In such an embodiment, any subsequent URL
processing can be omitted altogether and the resource may be immediately
be requested by the client computing device 102.

[0034] In both the embodiment in which a URL is modified or replaced by an
IP address of a cache server component, the translation information can
include rules or other information that specifies the applicability of
the various identified domains/IP addresses to the original URLs, the
manner in which an original URL is to be modified, expiration timeframes
for the translation information and the like. The translation information
is then returned to the requesting client computing device 102.

[0035] With reference now to FIG. 5, the client computing device 102
receives and processes the translation information from the CDN service
provider 106. In one embodiment, the translation information can include
data, or other information, that is processed by code existing on the
client computing device 102 in a manner as will be described below. For
example, the client computing device 102 may be executing a software
application configured specifically for the processing of the translation
code. Similarly, the translation execution code previously executed by
the client computing device 102 may include executable instructions for
processing the translation information. Alternatively, the translation
information can include executable instructions, such as script-based
instructions, that cause the client computing device 102, such as through
a browser software application, to process other data in the translation
information.

[0036] As described above, the processing of the translation information
results in the modification, or replacement, of the original URL,
referred to generally as the translated identifier. In one embodiment,
the translation process results in the identification of an IP address of
a cache server component that will process the request for the associated
resource. In this embodiment, the no additional translation or URL
processing steps are required.

[0037] In another embodiment, the processing of the translation
information results in the generation of a URL that may require
additional processing. Specifically, in this embodiment, the translated
identifier is a translated URL modified such that requests for the
resources associated with the translated URLs resolve to a POP associated
with the CDN service provider 106. In one embodiment, the translated URL
identifies the domain of the CDN service provider 106 (e.g.,
"cdnprovider.com"), the same name of the resource to be requested (e.g.,
"resource.xxx") and the same path where the resource will be found (e.g.,
"path"). Additionally, the translated URL can include additional
processing information (e.g., "additional information"). The translated
URL would have the form of:

http://additional_information.cdnprovider.com/path/resources.xxx

[0038] In another embodiment, the information associated with the CDN
service provider 106 is included the modified URL, such as through
prepending or other techniques, such that the translated URL can maintain
all of the information associated with the original URL. In this
embodiment, the translated URL would have the form of:

[0039] As previously described, the translation information can include
rules, or other processing information, that can specify which original
URLs should be modified and/or the translation information that can be
used to modify specific original URLs. Still further, in another
embodiment, the processing of the requested content from the content
provider 104 may result in the request of the embedded original URLs
prior to the receipt of the translation information from the CDN service
provider 106. In one approach, the client computing device 102 may issue
one or more resource requests according to the information in the
original URL until the translation information is received and any
remaining original URLs can be translated. In another approach, the
original URLs can correspond to non-functional resource identifiers that
can only be processed upon completion of the translation process. In
still a further approach, the original URLs can correspond to
intermediary resource identifiers that can be partially processed by the
client computing device 102 upon the initial processing of the requested
content but that can only be finalized after completion of the
translation process. One skilled in the relevant art will appreciate that
the particular technique for translation and the management of URL
translation in advance of the issuance of resource requests may vary
according to the type of software application generating the resource
requests, the specific capabilities of the networking protocol, the
specific rules associated with the processing of the markup language (or
other information) of the requested content, and the combination thereof.

[0040] With continued reference to FIG. 5, upon completion of the resource
identification translation process, the browser application of the client
computing device 102 initiates the request for the resources identified
by the translated identifier. In accordance with an illustrative
embodiment related to a translated identifier that is an IP address, the
request for content is directly sent to the cache server associated by
the translated IP address.

[0041] In accordance with an illustrative embodiment related to a
translated URL and with reference to the illustrative example of the
translated URL "http://additional
information.contentprovider.com/path/resource.xxx", the request for an
embedded resource associated with a URL by the client computing device
102 corresponds to a first DNS query for the translated URL that results
in the identification of a DNS server authoritative to the "." and the
"com" portions of the translated URL. After resolving the "." and "com"
portions of the embedded URL, the client computing device 102 then issues
a subsequent DNS query for the translated URL that results in the
identification of a DNS server authoritative to the ".cdnprovider"
portion of the embedded URL.

[0042] In a manner similarly describe above, in an illustrative
embodiment, the successful resolution of the "cdnprovider" portion of the
translated URL identifies the IP address of a DNS server, or server,
associated with CDN service provider 116. In a manner similarly described
above, in one embodiment, the resolution of this portion of the
translated URL can result in the identification a specific network
address, such as a specific IP address, of a DNS server component of a
POP. In another embodiment, the resolution of this portion of the
translated URL can result in the identification of a network address
shared by one or more POPs. In this embodiment, a further DNS request to
the shared IP address utilizes a one-to-many network routing schema, such
as anycast, such a specific POP will receive the request as a function of
network topology.

[0043] In either of the above identified embodiments, a specific DNS
server in the DNS component 118 of a POP 116 receives a DNS query. Once
one of the DNS servers receives the request, the DNS server 118
identifies a cache server component that can provider the requested
resource, such as cache component 120. Although in the illustrative
example, the DNS component 118 selects the local cache component 120, one
skilled in the relevant art will appreciate that the DNS server 118 may
implement any manner of additional processing techniques for selecting a
specific cache component of other POPs or a specific caching server
computing device within any one of the POPs associated with the CDN
service provider 106. Upon identification of a cache server, the DNS
server provides an IP address of the cache server to the requesting
client computing device 102. The client computer can then utilize
communication protocols to acquire the resources from a cache server
identified by the IP address. The requested resources are then processed
by the browser application as appropriate.

[0044] With reference now to FIG. 6, in an illustrative embodiment, the
translation information may be cached or otherwise stored by the client
computing device 102 for subsequent content requests. For example, if the
translation information is associated with expiration data, the
translation information may be maintained by the client computing device
102 until the expiration time has lapsed. In this embodiment, as
previously described with regard to FIG. 3, the client computing device
102 generates a subsequent content request that is received and processed
by the content provider 104, such as through the Web server 110. For
example, the subsequent request for content can correspond to a request
for another Web page associated with the content provider.

[0045] Upon receipt of the content request, the content provider again
identifies the appropriate responsive content. As described above, the
requested content can correspond to a Web page that is displayed on the
client computing device 102 via the processing of information. The
requested content can also include a number of embedded resource
identifiers that corresponds to resource objects that should be obtained
by the client computing device 102 as part of the processing of the
requested content. Additionally, the requested content will also include
the embedded translation execution code previously provided by the CDN
service provider 106. The responsive content is returned to the client
computing device 102.

[0046] With reference now to FIG. 7, upon receipt of the requested content
with the embedded translation executable code, the client computing
device 102 can re-execute the process for requesting the translation
information from the CDN service provider 106 as described with regard to
FIG. 4. This may occur if the client computing device 102 cannot cache
translation information, the cache translation information has expired or
is considered to be corrupt, and the like. Alternatively, if the
translation information is cached, the client computing device 102 can
begin to immediately translate the original URLs embedded in the
subsequent content provided by the content provider 104 in the manner
described above. Some or all of the cached translation information could
be used in lieu of obtaining the translation information or updated
translation information from the CDN service provider 106. For purposes
of illustration, the proper resolution of the translated URLs of the
subsequent content request are resolved to a different POP, POP 128,
which provides the requested resource to the client computing device 102.

[0047] With reference now to FIG. 8, a resource identifier processing
routine 800 implemented by a client computing device 102 to process
embedded resource identifiers with translation information will be
described. At block 802, client computing device 102 transmits the
original request for content. As described above, the request for content
may directed to a Web server 110 of the content provider 104. At block
804, the client computing device 102 obtains responsive content that
includes translation request code. As described above, in an illustrative
embodiment, the translation request code can correspond to script-based
instructions that can be processed by a software application running on
the client computing device 102. Still further, the translation request
code can be organized in the responsive content such that the translation
request is the first (in accordance with the limitations of the
limitations/capabilities of the networking protocols and markup language)
data processed by the client computing device 102.

[0048] At block 806, the client computing device 102 transmits the request
for translation information to the CDN service provider 106 identified in
the translation execution code. As previously described, the request for
translation information can include information that may be used by the
CDN service provider 106 to generate, or select, the translation
information. The additional information may be specifically included in
the request for translation or inferred from aspects of the request
(e.g., IP address of the client computing device 102). At block 808, the
client computing device 102 obtains translation information from the CDN
service provider 106.

[0049] At block 810, the client computing device 102 processes the
embedded resource identifiers with the translation information. As
previously described, the translation information can include data
utilized to another software application to process the embedded,
original URLs (such as a stand alone software application).
Alternatively, the translation information can include instructions (such
as script-based instructions) that call a software application (such as a
browser application) to process the remaining portions of the translation
information. As also previously described, the processing of the
original, embedded URLs can correspond to the modification (including
replacement) of the URLs such that a request for the resource associated
with the embedded resource resolves to a POP associated with the CDN
service provider 106. In still a further embodiment, the original URLs
may be directly translated into an IP address of a cache server component
such that further DNS resolution is not necessary. Any one of a variety
of techniques or combination of techniques, some of which were previously
illustrated, could be utilized to modify the original URLs.

[0050] At block 812, the client computing device 102 transmits requests
for the resources associated with the translated URLs. In an illustrative
embodiment, the request for the resources associated with the translated
URLs can be facilitated through various networking protocols. At block
814, the routine 800 terminates. Additionally, the routine 800 can be
implemented again to process resource identifiers received in subsequent
content requests. In this application, however, blocks 806 and 808 may be
omitted with the utilization of cached translation information obtained
from a previous iteration of routine 800.

[0051] While illustrative embodiments have been disclosed and discussed,
one skilled in the relevant art will appreciate that additional or
alternative embodiments may be implemented within the spirit and scope of
the present invention. Additionally, although many embodiments have been
indicated as illustrative, one skilled in the relevant art will
appreciate that the illustrative embodiments do not need to be combined
or implemented together. As such, some illustrative embodiments do not
need to be utilized or implemented in accordance with scope of variations
to the present disclosure.

[0052] Conditional language, such as, among others, "can," "could,"
"might," or "may," unless specifically stated otherwise, or otherwise
understood within the context as used, is generally intended to convey
that certain embodiments include, while other embodiments do not include,
certain features, elements and/or steps. Thus, such conditional language
is not generally intended to imply that features, elements and/or steps
are in any way required for one or more embodiments or that one or more
embodiments necessarily include logic for deciding, with or without user
input or prompting, whether these features, elements and/or steps are
included or are to be performed in any particular embodiment.

[0053] Any process descriptions, elements, or blocks in the flow diagrams
described herein and/or depicted in the attached figures should be
understood as potentially representing modules, segments, or portions of
code which include one or more executable instructions for implementing
specific logical functions or steps in the process. Alternate
implementations are included within the scope of the embodiments
described herein in which elements or functions may be deleted, executed
out of order from that shown or discussed, including substantially
concurrently or in reverse order, depending on the functionality
involved, as would be understood by those skilled in the art. It will
further be appreciated that the data and/or components described above
may be stored on a computer-readable medium and loaded into memory of the
computing device using a drive mechanism associated with a computer
readable storing the computer executable components such as a CD-ROM,
DVD-ROM, or network interface further, the component and/or data can be
included in a single device or distributed in any manner. Accordingly,
general purpose computing devices may be configured to implement the
processes, algorithms and methodology of the present disclosure with the
processing and/or execution of the various data and/or components
described above.

[0054] It should be emphasized that many variations and modifications may
be made to the above-described embodiments, the elements of which are to
be understood as being among other acceptable examples. All such
modifications and variations are intended to be included herein within
the scope of this disclosure and protected by the following claims.