Method and system for packing and unpacking web pages

• US 20050050461A1
• Filed: 10/08/2004
• Published: 03/03/2005
• Est. Priority Date: 06/06/2000
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hall, Gabriel J., Ramaley, Alan
• Granted Patent: US 7,464,328 B2
• Time in Patent Office: Days
• US Class Current: 715/205
• CPC Class Codes: G06F 16/957 Browsing optimisation, e.g. caching or content distillation

Abstract

A method for packing the multiple files and folders of an HTML Web page into a single MHTML file. The packing process begins by determining whether the user has write privileges to the current location. If not, the user is prompted to save the MHTML file in an alternate location (e.g., the desktop). If the user has write privileges to the current location, the process opens the main HTML Web page and searches for supporting resource files. In short, the supporting resource files are identified by searching for known, common resource file references in the main HTML source file. When the resource file references have been identified, the process packages the main HTML document and all of the supporting resource files into a single file in MHTML format. The unpacking process opens the MHTML file and identifies the main HTML document portion, as well as the portions of the MHTML file containing the supporting resource files. Once all of the components have been identified, the Web page'"'"'s folder structure is determined by referring to the content location field contained in each separate portion of the MHTML file. The individual MHTML components are converted into files and the main HTML file is stored. The resource files are stored in locations relative to the main HTML file, as identified by the unpacked folder structure.

Claims

1-14. -14. (Canceled)

15. A method for packing a page as single file, the method comprising:

receiving an indication that a user has selected through a shell or file dialog a page representation corresponding to a main markup language document of the page, and in response to receiving the indication, displaying a selectable representation associated with packaging the page into a single file;

receiving an indication that the user has selected the representation associated with packaging the page into a single file;

in response to receiving the selection associated with packaging the page, making a determination as to whether the file includes at least one link to at least one resource file;

in response to a determination that the file includes at least one link to at least one resource file, packing the file and the at least one resource file into a single file;

wherein packing the file and the at least one resource file into a single file comprises

storing a main markup language document of the page as a first component of the packaged file, the first component having a first content-location description corresponding to the location of the main markup language document,

storing the at least one resource file as a second component of the packaged file, the second component having a second content-location description corresponding to the location of the at least one resource file, and

wherein the first content-location description and the second content-location description define a folder structure corresponding to locations of the file and the resource file in relation to each other; and

displaying a representation of the packaged page file in the shell or file dialog containing the page representation corresponding to the main markup language document of the page.

16. The method recited in claim 15 wherein the main markup language document of the page comprises a main HTML document of a Web page.

17. The method recited in claim 16 wherein the single file is an MHTML file.

18. The method recited in claim 17, further comprising:

determining that a user desires to unpack the MHTML page file;

extracting a leaf name from the content-location description to be used as the name of the HTML page file;

comparing the content-location description of each MIME part of the MHTML file with the content-location description of the main HTML part of the MHTML file;

creating a folder structure corresponding to the content-location descriptions of the main HTML file and the MIME parts, wherein the folder structure includes a generic folder for storage of supporting files that do not have a content-location description;

for each MIME part, determining if the supporting file is in the same folder as the main HTML file or in a subfolder below the main file;

if the supporting file is in the same folder as the main HTML file or in a subfolder below the main file, converting the MIME part into HTML and saving the supporting file in the folder designated by the content-location description; and

if the supporting file is not in the same folder as the main HTML file and is not in a subfolder below the main file, converting the MIME part into HTML and saving the supporting file in the generic folder.

19. The method recited in claim 18, further comprising:

for each MIME part, determining if a leaf name can be extracted from the content-location description;

if a leaf name for the supporting file can be extracted, saving the supporting file with the leaf name in the folder designated by the content-location description; and

if a leaf name for the supporting file cannot be extracted, assigning the file a name corresponding to the number of supporting files previously saved without an extracted leaf name, and attaching a file extension corresponding to a content-type description stored with the supporting file as a component of the MHTML file.

20. A computer-readable medium having computer-executable instructions for performing the method recited in claim 15.

21. A computer-implemented method for packing a page as a single file, the method comprising:

receiving an indication that a user has selected a representation corresponding to a markup language source file associated with the page, and in response to receiving the indication, displaying a selectable representation associated with packaging the page into a single file;

receiving an indication that the user has selected the representation associated with packaging the page into a single file;

opening the markup language source file associated with the page;

parsing the markup language source file searching for supporting files;

gathering a list of supporting files; and

packing the supporting files and the markup language source file into a single file, wherein each supporting file is added to the single file by assigning each supporting file a content-location description set to the location of the supporting file and a separate content-type description.

22. The method recited in claim 21 wherein the markup language source file associated with the page comprises a main HTML document of a Web page.

23. The method recited in claim 21 wherein the single file is a MHTML file.

24. The method recited in claim 23 wherein the steps of parsing the markup language source file and gathering a list of supporting files comprises gathering a list of all the files necessary to render the page.

25. The method recited in claim 23, further comprising:

determining that a user desires to unpack the MHTML page file;

extracting a leaf name from the content-location description to be used as the name of the HTML page file;

comparing the content-location description of each MIME part of the MHTML file with the content-location description of the main HTML part of the MHTML file;

creating a folder structure corresponding to the content-location descriptions of the main HTML file and the MIME parts, wherein the folder structure includes a generic folder for storage of supporting files that do not have a content-location description;

for each MIME part, determining if the supporting file is in the same folder as the main HTML file or in a subfolder below the main file;

if the supporting file is in the same folder as the main HTML file or in a subfolder below the main file, converting the MIME part into HTML and saving the supporting file in the folder designated by the content-location description; and

if the supporting file is not in the same folder as the main HTML file and is not in a subfolder below the main file, converting the MIME part into HTML and saving the supporting file in the generic folder.

26. The method recited in claim 25, further comprising:

for each MIME part, determining if a leaf name can be extracted from the content-location description;

if a leaf name for the supporting file can be extracted, saving the supporting file with the leaf name in the folder designated by the content-location description; and

if a leaf name for the supporting file cannot be extracted, assigning the file a name corresponding to the number of supporting files previously saved without an extracted leaf name, and attaching a file extension corresponding to a content-type description stored with the supporting file as a component of the MHTML file.

27. A method for unpacking an MHTML page file, having a main markup language part and at least one MIME part corresponding to at least one supporting file, to markup language format, the method comprising:

determining that a user desires to unpack an MHTML page file;

making a determination as to whether the main markup language part of the MHTML file has a content-location description;

if the main markup language part of the MHTML file has a content-location description,

extracting a leaf name from the content-location description to be used as the name of the markup language page file;

comparing the content-location description of each MIME part of the MHTML file with the content-location description of the main markup language part of the MHTML file;

creating a folder structure corresponding to the content-location descriptions of the main markup language file and the MIME parts, wherein the folder structure includes a generic folder for storage of supporting files that do not have a content-location description;

for each MIME part, determining if the supporting file is in the same folder as the main markup language file or in a subfolder below the main file;

if the supporting file is in the same folder as the main markup language file or in a subfolder below the main file, converting the MIME part into markup language and saving the supporting file in the folder designated by the content-location description; and

if the supporting file is not in the same folder as the main markup language file and is not in a subfolder below the main file, converting the MIME part into markup language and saving the supporting file in the generic folder.

28. The method recited in claim 27 wherein the main markup language file comprises a main HTML document of a Web page.

29. The method recited in claim 27, wherein if the main markup language part of the MHTML file does not have a content-location description, the method further comprising:

using the name of the MHTML file selected by the user as the name of the markup language page file; and

converting each MIME part into markup language and saving the supporting file in the generic folder.

30. The method recited in claim 27, wherein determining that a user desires to unpack an MHTML page file comprises:

receiving an indication that a user has selected the MHTML page file through a shell or file dialog;

in response to receiving the indication, displaying a selectable representation associated with unpacking the file; and

receiving an indication that the user has selected the representation associated with unpacking the file.

31. A computer-readable medium having computer-executable instructions for performing the method recited in claim 27.

32. The method recited in claim 27, wherein comparing the content-location description of each MIME part of the MHTML file with the content-location description of the main markup language part of the MHTML file further comprises:

if the main markup language part of the MHTML file does not have a content-location description, locating the supporting file inside the generic folder, wherein the generic folder is named after a name of the MHTML page.

33. The method recited in claim 27, wherein comparing the content-location description of each MIME part of the MHTML file with the content-location description of the main markup language part of the MHTML file further comprises:

determining whether the supporting file has a content-location description; and

if not, then locating the supporting file inside the generic folder, wherein the generic folder is named after a name of the MHTML page.

34. The method recited in claim 27, wherein comparing the content-location description of each MIME part of the MHTML file with the content-location description of the main markup language part of the MHTML file further comprises:

determining whether the supporting file has a file name within the content-location description; and

if not, then locating the supporting file inside the generic folder, wherein the generic folder is named after a name of the MHTML page.