Apparatus and computer-readable media for determining whether an existing map specifies a different content type than the content type that is specified for the specified resource name extension in a web distributed authoring and versioning (WebDAV) request

• US 7,689,564 B2
• Filed: 09/30/2004
• Issued: 03/30/2010
• Est. Priority Date: 07/26/1999
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Van, Van C., Soderberg, Joel M., Deen, Brian J., Sanders, Henry L.
• Primary Examiner(s): Channavajjala; Srirama
• Application Number:
  US10/954,746
• Publication Number:
  US 20050055333A1
• Time in Patent Office: 2,007 Days
• Field of Search: 709220-226, 709217-219, 709/203, 707 1- 2, 707/10, 707/100, 707/102, 707/103.X, 707/104.1, 707/200, 707/203, 718/1
• US Class Current: 1/1
• CPC Class Codes: H04L 2101/30 Types of network names
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/301 Name conversion
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

Various embodiments of the invention are directed to closely integrating functionality between an internet server and a WebDAV tool. Areas of specific focus in this document include delegation of duties between the internet server and the WebDAV tool, efficient management of a resource'"'"'s content-type, support for segregation of a namespace into separate virtual roots, and determinations of whether to invoke certain processing extensions to handle requests for a given HTTP verb.

Claims

1. A computer readable storage medium having computer-executable instructions which, when executed by a computer, perform steps comprising:

receiving at a computer system a request that specifies a resource name extension and a content type respectively from a plurality of resource name extensions and a plurality of content types, wherein;

in an event the specified resource name extension of the plurality of resource name extensions is associated with more than the specified content type of the plurality of content types, creating a new multi-purpose internet mail extension (MIME) map for a URL'"'"'s complete namespace containing only a mapping for a URL extension to the specified content type, wherein the new MIME map for the URL'"'"'s complete namespace containing only the mapping for the URL extension to the specified content type ensures that only the existing specified resource is scoped by the new MIME map; and

in an event the specified resource name extension of the plurality of resource name extensions is not associated with any content type of the plurality of content types in a particular MIME map, determining whether an association exists between the specified extension and any existing content type in any scoping MIME map, and when no association exists between the specified resource name extension and any existing content type in any scoping MIME map, creating a new entry for the particular MIME map for the specified resource name extension and the specified content type;

ascertaining whether current mapping scenarios that map resource name extensions to content types are adequate to map the specified resource name extension to the specified content type, wherein the ascertaining comprises determining whether an existing map specifies a different content type than the content type that is specified for the specified resource name extension in a Web Distributed Authoring and Versioning (WebDAV) request;

in an event there is no MIME map mapping the specified resource name extension of the plurality of resource name extensions associated with the specified content type of the plurality of content types, creating a new mapping scenario that maps the specified resource name extension to the specified content type if the current mapping scenarios are not sufficient to map the specified name extension to the specified content type, wherein creating a new mapping scenario comprises setting a content-type property for a resource that is associated with the specified resource name extension; and

the computer system storing the new mapping scenario in a computer-readable storage medium.

2. A computer-implemented method, comprising:

receiving by at least one computer a request that specifies a resource name extension and a content type respectively from a plurality of resource name extensions and a plurality of content types, wherein;

in an event the specified resource name extension of the plurality of resource name extensions is associated with more than the specified content type of the plurality of content types, creating a new multi-purpose internet mail extension (MIME) map for a URL'"'"'s complete namespace containing only a mapping for a URL extension to the specified content type, wherein the new MIME map for the URL'"'"'s complete namespace containing only the mapping for the URL extension to the specified content type ensures that only the existing specified resource is scoped by the new MIME map; and

in an event the specified resource name extension of the plurality of resource name extensions is not associated with any content type of the plurality of content types in a particular MIME map, determining whether an association exists between the specified extension and any existing content type in any scoping MIME map, and when no association exists between the specified resource name extension and any existing content type in any scoping MIME map, creating a new entry for the particular MIME map for the specified resource name extension and the specified content type;

ascertaining by the at least one computer whether current mapping scenarios that map resource name extensions to content types are adequate to map the specified resource name extension to the specified content type, wherein the ascertaining comprises determining whether an existing mare specifies a different content type than the content type that is specified for the specified resource name extension in a Web Distributed Authoring and Versioning (WebDAV) request;

in an event there is no MIME map mapping the specified resource name extension of the plurality of resource name extensions associated with the specified content type of the plurality of content types, creating a new mapping scenario that maps the specified resource name extension to the specified content type if the current mapping scenarios are not sufficient to map the specified name extension to the specified content type, wherein creating a new mapping scenario comprises setting a content-type property for a resource that is associated with the specified resource name extension; and

storing the new mapping scenario in a computer-readable storage medium.

3. A computer-readable storage medium having computer-executable instructions stored thereon, the instructions when executed causing one or more processors to perform acts comprising:

facilitating hosting a resource in a virtual server namespace such that a content type returned in response to a Web Distributed Authoring and Versioning (WebDAV) GET request is the same content type received with a WebDAV PUT request from a client;

receiving the WebDAV PUT request which specifies a resource name extension and content type pair for a resource;

ascertaining whether a multi-purpose internet mail extension (MIME) map exists for the WebDAV PUT request, the specified resource name extension, and content type pair which scopes the resource, wherein scope indicates the specified content type and the specified resource name extension corresponding to the resource are available in the namespace, and wherein ascertaining whether a MIME map exists comprises;

in an event that there is not a MIME map for the specified content-type and extension pair, creating a new MIME map for the virtual server namespace hosting the resource;

in an event that a particular MIME map includes an entry for the specified resource name extension, but no entry for content type, determining whether an association exists between the extension and any existing content type in any scoping MIME map, and when no association exists between the extension and any existing content type in any scoping MIME map, creating a new entry for the particular MIME map for the specified resource name extension and content type pair which scopes the resource;

in an event that the WebDAV PUT request specifies a content type for a particular extension which is different from a content type defined for the particular extension in a scoping MIME map, determining whether another existing MIME map stipulates a different content type than the WebDAV PUT request, and when another existing MIME map stipulates a different content type than the WebDAV PUT request, creating a new MIME map for a URL'"'"'s complete namespace containing only the mapping for a URL extension to the specified content type, wherein the new MIME map for the URL'"'"'s complete namespace containing only the mapping for the URL extension to the specified content type ensures that only the existing, specified resource is scoped by the new MIME map, wherein a property-setting capability of WebDAV is utilized for creating new MIME mans which facilitate setting content types for a plurality of specific resources as properties for the plurality of specific resources such that a correct content type is returned for each resource when the resource is requested; and

hosting the resource in a virtual server namespace based on the particular MIME map that maps the specified resource name extension and content type pair.

4. The computer-readable storage medium of claim 3, wherein the virtual namespace has at least one virtual root, wherein a virtual root facilitates scoping namespaces with custom attributes.

5. The computer-readable storage medium of claim 3, wherein the virtual namespace has at least one virtual root that points to a different physical location.