HTTP server and recording medium recoding HTTP server program
AssigneeMurata Kikai Kabushiki Kaisha
InventorYoshifumi Tanimoto
Life of this patent
Estimating the term…
Loading patent…
AssigneeMurata Kikai Kabushiki Kaisha
InventorYoshifumi Tanimoto
Estimating the term…
A Hyper Text Transfer Protocol (HTTP) server includes a storage device that store processing status identification information which identifies a condition for changing a status for content by assigning a corresponding file name to each content and a transmitter that transmits the file name of the content stored in the storage device and processing status identification information in accordance with a request from a HTTP client.
A Hyper Text Transfer Protocol (HTTP) server comprising:
A Hyper Text Transfer Protocol (HTTP) server comprising:
A recording medium recording a program for a computer to function as a Hyper Text Transfer Protocol (HTTP) server, comprising:
A Hyper Text Transfer Protocol (HTTP) server comprising:
Dependencies are inferred from the claim text.
Drawings are temporarily unavailable. Open the PDF at USPTO
No related US applications are recorded in the indexed filing history.
Backward citations are indexed for grants only.
Protocols: based on web technology, e.g. hypertext transfer protocol [HTTP]
Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions: in the application layer [OSI layer 7]
Digital communication
Term end not estimated
The present invention relates to a Hypertext Transfer Protocol (HTTP) server.
A HTTP server assigns Uniform Resource Locators (URL) to a storage unit or the like, and stores in the storage unit or the like, a Hypertext Markup Language (HTML) file and content formed from image data. By designating the URL and transmitting the HTML file requested from a HTTP client in accordance with a communication based on the HTTP protocol, character information and the content formed from image data are displayed on a browser of the HTTP client. Further, the details of the HTTP protocol are shown in Request for Comments (RFC) 1945 of the Internet Engineering Task Force (IETF) or the like. The details of the HTML document are shown in RFC 1866 of the IETF or the like.
There are cases when the transmission and reception of the HTML file and the image data carried out between the HTTP server and a client are used for exchanging an original document that is to be transmitted by a facsimile between the HTTP clients. That is, first, one of the HTTP clients uploads the image data of the original document to be transmitted and the HTML file and downloads the image data to the HTTP server. Then, the other HTTP client designates the URL indicating the HTML file, and downloads the uploaded HTML file and the image data of the original document. Accordingly, the original document can be transmitted from one of the HTTP clients to the other HTTP client.
FIG. 1 is a view showing an example of a network environment where the HTTP server of an embodiment of the present invention is provided.
FIG. 2 is a view showing an example of a configuration of the HTTP server of an embodiment of the present invention.
FIG. 3 is a flowchart showing an operation of the HTTP server of when the content is uploaded to the HTTP server.
A Hyper Text Transfer Protocol (HTTP) server according to an embodiment of the present invention will be described with reference to the accompanying drawings. FIG. 1 shows an example of a network environment A where the HTTP server 1 is provided. The HTTP server 1 is connected to a Local Area Network (LAN) 2. The HTTP server 1 can communicate with a plurality of client personal computers (client PCs) 3 that are also connected to the LAN 2 in accordance with the HTTP. Moreover, the HTTP server 1 can communicate with a router 4 that is provided on the LAN 2, and also with other client PCs 3 through the Internet in accordance with the HTTP protocol.
As shown in FIG. 2, for example, the HTTP server 1 includes a Central Processing Unit (CPU) 5, a Random Access Memory (RAM) 6, a Read Only Memory (ROM) 7, a display 8, an input device 9, a LAN interface 10, and a bus 11. The CPU 5 controls each part of the HTTP server 1 in accordance with a prescribed program. The RAM 6 stores content 12, a table 13 or the like that are to be described later on. The ROM 7 stores a HTTP control program that is necessary for the HTTP server 1 to communicate by the HTTP protocol, a control program for executing an operation shown in the flowchart to be described later on. The display 8 displays and provides various information to an operator or the like. The input device 9 includes a mouse, a keyboard, or the like. The LAN interface 10 connects the LAN 2 and the HTTP server 1 such that the communication can be carried out. The bus 11 connects each of the parts 5 through 10 such that the communication can be carried out.
Moreover, the HTTP server 1 includes a function as the HTTP server, and an electronic mail communication function. For carrying out a prescribed notification to be described later on, the HTTP server 1 generates an electronic mail describing a prescribed document, and transmits the electronic mail to a prescribed client PC.