CN102065143A - Communication method and system based on HTTP (hyper Text Transfer Protocol), HTTP server and HTTP client - Google Patents
Communication method and system based on HTTP (hyper Text Transfer Protocol), HTTP server and HTTP client Download PDFInfo
- Publication number
- CN102065143A CN102065143A CN2010106132010A CN201010613201A CN102065143A CN 102065143 A CN102065143 A CN 102065143A CN 2010106132010 A CN2010106132010 A CN 2010106132010A CN 201010613201 A CN201010613201 A CN 201010613201A CN 102065143 A CN102065143 A CN 102065143A
- Authority
- CN
- China
- Prior art keywords
- http
- server
- client
- connection
- type
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a communication method and system based on an HTTP (hyper Text Transfer Protocol), an HTTP server and an HTTP client. The method comprises the following steps that: a server receives an HTTP request message transmitted by a client through a concurrence type HTTP permanent connection, wherein the HTTP request message comprises a Transaction-Id header field; and the server returns an HTTP response message to the client through the concurrence type HTTP permanent connection, wherein the HTTP response message includes the Transaction-Id header field.
Description
Technical field
The embodiment of the invention relates to the communication technology, relates in particular to based on the communication means of HTML (Hypertext Markup Language) (Hyper TextTransfer Protocol, be called for short HTTP) and system, http server, HTTP client.
Background technology
In communication system, interface between server and the client can use based on HTML (Hypertext Markup Language) (Hyper Text Transfer Protocol, abbreviation HTTP) connecting is that HTTP connects, for example: IP Multimedia System (IP Multimedia Subsystem, be called for short IMS) in, application server (Application Server, be called for short AS) with Multimedia resource function controller (MRFC) (Multimedia Resource Function Controller is called for short MRFC) between Sr interface.Wherein, above-mentioned HTTP connects can comprise two kinds of connections, and a kind of HTTP of being connects temporarily, and a kind of HTTP of being forever connects.Above-mentioned two kinds of HTTP connect and need set up before user end to server be initiated the HTTP request, and the former removes after client is returned http response at server, and the latter is dismounting when sending without any message in the HTTP connection of setting up in a period of time.Therefore, be connected with dismounting HTTP for fear of the HTTP connection of setting up that repeats, above-mentioned interface can use HTTP forever to connect.The permanent connection of HTTP can comprise two types, and a kind of is that the HTTP of parallel (parallelism) mode forever connects, and another kind is that the HTTP of streamline (pipelining) type forever connects.When existing a plurality of users to initiate the HTTP request by user end to server simultaneously, the former need set up many HTTP simultaneously and forever connect the HTTP request that could realize handling simultaneously with parallel mode a plurality of users, and the latter only needs permanent connection of the HTTP of a streamline type just can realize that the HTTP that handles a plurality of users with pipeline system successively asks.
In the above-mentioned prior art, if the interface that uses HTTP to connect uses the HTTP of parallel mode forever to connect, need set up many HTTP simultaneously and forever connect, could realize handling simultaneously a plurality of users' HTTP request, increase the complexity that interface configuration administers and maintains with parallel mode; If the interface that uses HTTP to connect uses the HTTP of streamline type forever to connect, need carry out order-preserving with http response to the HTTP request, reduced the efficient of interface.
Summary of the invention
The embodiment of the invention provides based on the communication means of HTTP and system, http server, HTTP client, in order to reducing the complexity that the interface configuration of using HTTP to connect administers and maintains, and improves the efficient of using the interface that HTTP connects.
The embodiment of the invention provides a kind of communication means based on HTTP, comprising:
Server forever connects the HTTP request message that receives the client transmission by the HTTP of concurrent type, comprises in the described HTTP request message to handle the identification information header field;
Described server returns http response message by permanent connection of the HTTP of described concurrent type to described client, comprises described processing identification information header field in the described http response message.
The embodiment of the invention provides another kind of communication means based on HTTP, comprising:
Client sends the HTTP request message by permanent the connection to server of the HTTP of concurrent type, comprises in the described HTTP request message and handles the identification information header field;
Described client forever connects the http response message that the described server of reception returns by the HTTP of described concurrent type, comprises described processing identification information header field in the described http response message.
The embodiment of the invention also provides a kind of http server, comprising:
Receiver module is used for forever connecting the HTTP request message that receives the client transmission by the HTTP of concurrent type, comprises in the described HTTP request message and handles the identification information header field;
Sending module is used for returning http response message by permanent connection of the HTTP of described concurrent type to described client, comprises described processing identification information header field in the described http response message.
The embodiment of the invention also provides a kind of HTTP client, comprising:
Sending module is used for sending the HTTP request message by permanent the connection to server of the HTTP of concurrent type, comprises in the described HTTP request message and handles the identification information header field;
Receiver module is used for forever connecting the http response message that the described server of reception returns by the HTTP of described concurrent type, comprises described processing identification information header field in the described http response message.
The embodiment of the invention provides a kind of communication system based on HTML (Hypertext Markup Language) HTTP again, comprises client and server, wherein:
Described client is used for sending the HTTP request message by permanent the connection to described server of the HTTP of concurrent type, comprise in the described HTTP request message and handle the identification information header field, and the HTTP by described concurrent type forever connects and receives the http response message that described server returns, and comprises described processing identification information header field in the described http response message;
Described server is used for forever connecting the described HTTP request message that receives described client transmission by the HTTP of described concurrent type, and by permanent connection of the HTTP of described concurrent type returning described http response message to described client.
As shown from the above technical solution, embodiment of the invention server forever connects the HTTP request message of handling the identification information header field that comprises that receives the client transmission by the HTTP of concurrent type, make it possible to return the http response message that comprises above-mentioned processing identification information header field to above-mentioned client by permanent connection of the HTTP of above-mentioned concurrent type, realized to handle a plurality of HTTP requests by the permanent connection of the HTTP of a concurrent type, thereby the complexity that the interface configuration that has reduced use HTTP connection administers and maintains, and the efficient that has improved the interface that uses the HTTP connection.
Description of drawings
In order to be illustrated more clearly in the embodiment of the invention or technical scheme of the prior art, to do one to the accompanying drawing of required use in embodiment or the description of the Prior Art below introduces simply, apparently, accompanying drawing in describing below is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to these accompanying drawings.
The schematic flow sheet of a kind of communication means based on HTTP that Fig. 1 provides for the embodiment of the invention one;
The another kind that Fig. 2 provides for the embodiment of the invention two is based on the schematic flow sheet of the communication means of HTTP;
The schematic flow sheet that Fig. 3 provides for the embodiment of the invention three based on the communication processing method of HTTP;
The structural representation of the http server that Fig. 4 provides for the embodiment of the invention four;
The structural representation of the HTTP client that Fig. 5 provides for the embodiment of the invention five;
The structural representation that Fig. 6 provides for the embodiment of the invention six based on the communication processing system of HTTP.
Embodiment
For the purpose, technical scheme and the advantage that make the embodiment of the invention clearer, below in conjunction with the accompanying drawing in the embodiment of the invention, technical scheme in the embodiment of the invention is clearly and completely described, obviously, described embodiment is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment among the present invention, those of ordinary skills belong to the scope of protection of the invention not making the every other embodiment that is obtained under the creative work prerequisite.
If the interface that uses HTTP to connect uses the HTTP of parallel (parallelism) mode forever to connect, need set up many HTTP simultaneously forever connects, could realize handling simultaneously a plurality of users' HTTP request, increase the complexity that interface configuration administers and maintains with parallel mode; If the interface that uses HTTP to connect uses the HTTP of streamline (pipelining) type forever to connect, need carry out order-preserving with http response to the HTTP request, reduced the efficient of interface.Therefore, the embodiment of the invention proposes another HTTP and forever connects, and the HTTP of promptly concurrent (concurrence) type forever connects.
The schematic flow sheet of a kind of communication means based on HTTP that Fig. 1 provides for the embodiment of the invention one, as shown in Figure 1, the communication means based on HTTP of present embodiment can may further comprise the steps:
HTTP request message wherein can include but not limited to GET request message, OPTIONS request message.
Particularly, above-mentioned processing identification information header field can be defined as a metric positive integer, span is 0～4294967295, the HTTP that can be used for concurrent type on permanent the connection http response message and the coupling of HTTP request message, concrete form can be as follows:
Transaction-Id＝″Transaction-Id″″:″1＊DIGIT
It will be understood by those skilled in the art that: if there is agency's (Proxy) equipment between client and the server, then this agent equipment needs to support the above-mentioned processing identification information of transparent transmission header field.
Http response message wherein can include but not limited to GET response message, OPTIONS response message.
Particularly, the above-mentioned HTTP response message is specifically as follows success response message, perhaps can also be failure response message.
Further, before above-mentioned steps 101, can further include above-mentioned server and above-mentioned client and carry out alternately, set up the permanent step of connecting of HTTP of above-mentioned concurrent type.Particularly, above-mentioned server receives that above-mentioned client sends sets up HTTP connection request message, comprise connection type (Connection-Type) header field in the above-mentioned HTTP of foundation connection request message, above-mentioned server is according to above-mentioned connection type header field, set up with above-mentioned client between the HTTP of concurrent type forever be connected.
Particularly, above-mentioned connection type header field can be used for indicating concurrent type or streamline type, set up the connection type header field indicating concurrent type that comprises in the HTTP connection request message if user end to server sends, the HTTP that then sets up concurrent type forever connects, if the connection type header field that comprises in the HTTP connection request message of setting up that user end to server sends is indicated the streamline type, the HTTP that then sets up the streamline type forever connects.Concrete form can be as follows:
Connection-Type＝″Connection-Type″″:″1#(connection-type)
connection-type＝pipelining|concurrence
Perhaps, above-mentioned connection type header field can also be used for the indicating concurrent type, if setting up that user end to server sends comprises this connection type header field in the HTTP connection request message, the HTTP that then sets up concurrent type forever connects, if setting up that user end to server sends do not comprise this connection type header field in the HTTP connection request message, the HTTP that then sets up the streamline type forever connects.Concrete form can be as follows:
Connection-Type＝″Connection-Type″″:″1#(connection-type)
connection-type＝concurrence
It will be understood by those skilled in the art that: if there is agency's (Proxy) equipment between client and the server, then this agent equipment needs to support the above-mentioned connection type header field of transparent transmission.
Further, if server is not supported above-mentioned connection type header field, can return 406 error messages to client, so that client is set up HTTP connection request message to what this server initiated not comprise this connection type header field again, according to method of the prior art, the HTTP that sets up the streamline type forever connects or the HTTP that sets up many parallel modes forever connects.
Further, when existing a plurality of users to initiate the HTTP request by user end to server simultaneously, the communication means that adopts present embodiment to provide based on HTTP, can forever connect by the HTTP of a concurrent type setting up, realize handling simultaneously a plurality of users' HTTP request in concurrent mode.
In the present embodiment, server forever connects the HTTP request message of handling the identification information header field that comprises that receives the client transmission by the HTTP of concurrent type, make it possible to return the http response message that comprises above-mentioned processing identification information header field to above-mentioned client by permanent connection of the HTTP of above-mentioned concurrent type, realized to handle a plurality of HTTP requests by the permanent connection of the HTTP of a concurrent type, thereby the complexity that the interface configuration that has reduced use HTTP connection administers and maintains, and the efficient that has improved the interface that uses the HTTP connection.
The another kind that Fig. 2 provides for the embodiment of the invention two is based on the schematic flow sheet of the communication means of HTTP, and as shown in Figure 2, the communication means based on HTTP of present embodiment can may further comprise the steps:
HTTP request message wherein can include but not limited to GET request message, OPTIONS request message.
Particularly, above-mentioned processing identification information header field can be defined as a metric positive integer, span is 0～4294967295, the HTTP that can be used for concurrent type on permanent the connection http response message and the coupling of HTTP request message, concrete form can be as follows:
Transaction-Id＝″Transaction-Id″″:″1＊DIGIT
It will be understood by those skilled in the art that: if there is agency's (Proxy) equipment between client and the server, then this agent equipment needs to support the above-mentioned processing identification information of transparent transmission header field.
Http response message wherein can include but not limited to GET response message, OPTIONS response message.
Particularly, the above-mentioned HTTP response message is specifically as follows success response message, perhaps can also be failure response message.
Further, before above-mentioned steps 101, can further include above-mentioned client and above-mentioned server and carry out alternately, set up the permanent step of connecting of HTTP of above-mentioned concurrent type.Particularly, above-mentioned client sends to above-mentioned server and sets up HTTP connection request message, comprise connection type (Connection-Type) header field in the above-mentioned HTTP of foundation connection request message, so that above-mentioned server is according to above-mentioned connection type header field, set up with above-mentioned client between the HTTP of concurrent type forever be connected.
Particularly, above-mentioned connection type header field can be used for indicating concurrent type or streamline type, set up the connection type header field indicating concurrent type that comprises in the HTTP connection request message if user end to server sends, the HTTP that then sets up concurrent type forever connects, if the connection type header field that comprises in the HTTP connection request message of setting up that user end to server sends is indicated the streamline type, the HTTP that then sets up the streamline type forever connects.Concrete form can be as follows:
Connection-Type＝″Connection-Type″″:″1#(connection-type)
connection-type＝pipelining|concurrence
Perhaps, above-mentioned connection type header field can also be used for the indicating concurrent type, if setting up that user end to server sends comprises this connection type header field in the HTTP connection request message, the HTTP that then sets up concurrent type forever connects, if setting up that user end to server sends do not comprise this connection type header field in the HTTP connection request message, the HTTP that then sets up the streamline type forever connects.Concrete form can be as follows:
Connection-Type＝″Connection-Type″″:″1#(connection-type)
connection-type＝concurrence
It will be understood by those skilled in the art that: if there is agency's (Proxy) equipment between client and the server, then this agent equipment needs to support the above-mentioned connection type header field of transparent transmission.
Further, if server is not supported above-mentioned connection type header field, can return 406 error messages to client, so that client is set up HTTP connection request message to what this server initiated not comprise this connection type header field again, according to method of the prior art, the HTTP that sets up the streamline type forever connects or the HTTP that sets up many parallel modes forever connects.
Further, when existing a plurality of users to initiate the HTTP request by user end to server simultaneously, the communication means that adopts present embodiment to provide based on HTTP, can forever connect by the HTTP of a concurrent type setting up, realize handling simultaneously a plurality of users' HTTP request in concurrent mode.
In the present embodiment, client sends the HTTP request message that comprises processing identification information header field by permanent the connection to server of the HTTP of concurrent type, make it possible to forever connect the http response message that comprises above-mentioned processing identification information header field that the above-mentioned server of reception returns by the HTTP of above-mentioned concurrent type, realized to handle a plurality of HTTP requests by the permanent connection of the HTTP of a concurrent type, thereby the complexity that the interface configuration that has reduced use HTTP connection administers and maintains, and the efficient that has improved the interface that uses the HTTP connection.
With IMS is example, and the technical scheme of the invention described above embodiment one and the invention described above embodiment two is elaborated.The schematic flow sheet that Fig. 3 provides for the embodiment of the invention three based on the communication processing method of HTTP, as shown in Figure 3, the communication processing method based on HTTP of present embodiment can may further comprise the steps:
Step 302, AS be according to above-mentioned connection type header field, set up with MRFC between the HTTP of concurrent type forever be connected, and return to MRFC and to set up the HTTP connection response message;
For example:
For example:
In the present embodiment, MRFC sends the HTTP request message that comprises processing identification information header field by permanent the connection to AS of the HTTP of concurrent type, make AS to return the http response message that comprises above-mentioned processing identification information header field to MRFC by permanent connection of the HTTP of above-mentioned concurrent type, realized to handle a plurality of HTTP requests by the permanent connection of the HTTP of a concurrent type, thereby reduced the complexity of Sr interface configuration management and maintenance, and the efficient that has improved Sr interface.
Need to prove: for aforesaid each method embodiment, for simple description, so it all is expressed as a series of combination of actions, but those skilled in the art should know, the present invention is not subjected to the restriction of described sequence of movement, because according to the present invention, some step can adopt other orders or carry out simultaneously.Secondly, those skilled in the art also should know, the embodiment described in the specification all belongs to preferred embodiment, and related action and module might not be that the present invention is necessary.
In the above-described embodiments, the description of each embodiment is all emphasized particularly on different fields, do not have the part that describes in detail among certain embodiment, can be referring to the associated description of other embodiment.
The structural representation of the http server that Fig. 4 provides for the embodiment of the invention four, as shown in Figure 4, the http server of present embodiment can comprise receiver module 41 and sending module 42.Wherein, receiver module 41 forever connects the HTTP request message that receives the client transmission by the HTTP of concurrent type, comprise in the above-mentioned HTTP request message and handle the identification information header field, sending module 42 returns http response message by permanent connection of the HTTP of above-mentioned concurrent type to above-mentioned client, comprises above-mentioned processing identification information header field in the above-mentioned HTTP response message.
The http server that the function of AS all can be provided by the embodiment of the invention in server, the embodiment of the invention three among the invention described above embodiment one is realized.
In the present embodiment, receiver module forever connects the HTTP request message of handling the identification information header field that comprises that receives the client transmission by the HTTP of concurrent type, make sending module to return the http response message that comprises above-mentioned processing identification information header field to above-mentioned client by permanent connection of the HTTP of above-mentioned concurrent type, realized to handle a plurality of HTTP requests by the permanent connection of the HTTP of a concurrent type, thereby the complexity that the interface configuration that has reduced use HTTP connection administers and maintains, and the efficient that has improved the interface that uses the HTTP connection.
Further, the http server of present embodiment can further include sets up module 43, is used for carrying out alternately with above-mentioned client, and the HTTP that sets up above-mentioned concurrent type forever connects.Particularly, set up module 43 and can be used to specifically to receive that above-mentioned client sends sets up HTTP connection request message, comprise the connection type header field in the above-mentioned HTTP of foundation connection request message, according to above-mentioned connection type header field, set up with above-mentioned client between the HTTP of concurrent type forever be connected.
The structural representation of the HTTP client that Fig. 5 provides for the embodiment of the invention five, as shown in Figure 5, the HTTP client of present embodiment can comprise sending module 51 and receiver module 52.Wherein, sending module 51 sends the HTTP request message by permanent the connection to server of the HTTP of concurrent type, comprise in the above-mentioned HTTP request message and handle the identification information header field, receiver module 52 forever connects the http response message that the above-mentioned server of reception returns by the HTTP of above-mentioned concurrent type, comprises above-mentioned processing identification information header field in the above-mentioned HTTP response message.
The HTTP client that the function of MRFC all can be provided by the embodiment of the invention in client, the embodiment of the invention three among the invention described above embodiment two realizes.
In the present embodiment, sending module sends the HTTP request message that comprises processing identification information header field by permanent the connection to server of the HTTP of concurrent type, make receiver module forever to connect and receive the http response message that comprises above-mentioned processing identification information header field that above-mentioned server returns by the HTTP of above-mentioned concurrent type, realized to handle a plurality of HTTP requests by the permanent connection of the HTTP of a concurrent type, thereby the complexity that the interface configuration that has reduced use HTTP connection administers and maintains, and the efficient that has improved the interface that uses the HTTP connection.
Further, the HTTP client of present embodiment can further include sets up module 53, is used for carrying out alternately with above-mentioned server, and the HTTP that sets up above-mentioned concurrent type forever connects.Particularly, setting up module 53 specifically can be used for setting up HTTP connection request message to above-mentioned server transmission, comprise the connection type header field in the above-mentioned HTTP of foundation connection request message, so that above-mentioned server is according to above-mentioned connection type header field, set up with above-mentioned client between the HTTP of concurrent type forever be connected.
The structural representation that Fig. 6 provides for the embodiment of the invention six based on the communication processing system of HTTP, as shown in Figure 6, the communication processing system based on HTTP of present embodiment can comprise client 61 and server 62, wherein:
The function of MRFC all can be by realizing based on the client in the communication processing system of HTTP 61 that the embodiment of the invention provides in client, the embodiment of the invention three among the invention described above embodiment two; The function of AS all can be by realizing based on the server in the communication processing system of HTTP 62 that the embodiment of the invention provides in server, the embodiment of the invention three among the invention described above embodiment one.
In the present embodiment, server forever connects the HTTP request message of handling the identification information header field that comprises that receives the client transmission by the HTTP of concurrent type, make it possible to return the http response message that comprises above-mentioned processing identification information header field to above-mentioned client by permanent connection of the HTTP of above-mentioned concurrent type, realized to handle a plurality of HTTP requests by the permanent connection of the HTTP of a concurrent type, thereby the complexity that the interface configuration that has reduced use HTTP connection administers and maintains, and the efficient that has improved the interface that uses the HTTP connection.
Further, the client 61 in the present embodiment can also be further used for carrying out alternately with server 62, and the HTTP that sets up above-mentioned concurrent type forever connects; Correspondingly, server 62 can also be further used for carrying out alternately with client 61, and the HTTP that sets up above-mentioned concurrent type forever connects.
One of ordinary skill in the art will appreciate that: all or part of step that realizes said method embodiment can be finished by the relevant hardware of program command, aforesaid program can be stored in the computer read/write memory medium, this program is carried out the step that comprises said method embodiment when carrying out; And aforesaid storage medium comprises: various media that can be program code stored such as ROM, RAM, magnetic disc or CD.
It should be noted that at last: above embodiment only in order to technical scheme of the present invention to be described, is not intended to limit; Although with reference to previous embodiment the present invention is had been described in detail, those of ordinary skill in the art is to be understood that: it still can be made amendment to the technical scheme that aforementioned each embodiment put down in writing, and perhaps part technical characterictic wherein is equal to replacement; And these modifications or replacement do not make the essence of appropriate technical solution break away from the spirit and scope of various embodiments of the present invention technical scheme.
Claims (16)
1. the communication means based on HTML (Hypertext Markup Language) HTTP is characterized in that, comprising:
Server forever connects the HTTP request message that receives the client transmission by the HTTP of concurrent type, comprises in the described HTTP request message to handle the identification information header field;
Described server returns http response message by permanent connection of the HTTP of described concurrent type to described client, comprises described processing identification information header field in the described http response message.
2. method according to claim 1 is characterized in that, also comprises: described server and described client are carried out alternately, and the HTTP that sets up described concurrent type forever connects.
3. method according to claim 2 is characterized in that, described server and described client are carried out alternately, and permanent connection of HTTP of setting up described concurrent type comprises:
Described server receives that described client sends sets up HTTP connection request message, comprises the connection type header field in the described HTTP of foundation connection request message;
Described server is according to described connection type header field, set up with described client between the HTTP of concurrent type forever be connected.
4. according to the described method of the arbitrary claim of claim 1～3, it is characterized in that the permanent Sr interface that is used between IP Multimedia System IMS client and the server that connects of the HTTP of described concurrent type.
5. the communication means based on HTML (Hypertext Markup Language) HTTP is characterized in that, comprising:
Client sends the HTTP request message by permanent the connection to server of the HTTP of concurrent type, comprises in the described HTTP request message and handles the identification information header field;
Described client forever connects the http response message that the described server of reception returns by the HTTP of described concurrent type, comprises described processing identification information header field in the described http response message.
6. method according to claim 5 is characterized in that, also comprises: described client and described server carry out alternately, and the HTTP that sets up described concurrent type forever connects.
7. method according to claim 6 is characterized in that, described client and described server carry out alternately, and permanent connection of HTTP of setting up described concurrent type comprises:
Described client sends to described server and sets up HTTP connection request message, comprise the connection type header field in the described HTTP of foundation connection request message, so that described server is according to described connection type header field, set up with described client between the HTTP of concurrent type forever be connected.
8. according to the described method of the arbitrary claim of claim 5～7, it is characterized in that the permanent Sr interface that is used between IP Multimedia System IMS client and the server that connects of the HTTP of described concurrent type.
9. a HTML (Hypertext Markup Language) http server is characterized in that, comprising:
Receiver module is used for forever connecting the HTTP request message that receives the client transmission by the HTTP of concurrent type, comprises in the described HTTP request message and handles the identification information header field;
Sending module is used for returning http response message by permanent connection of the HTTP of described concurrent type to described client, comprises described processing identification information header field in the described http response message.
10. http server according to claim 9 is characterized in that, also comprises and sets up module, is used for carrying out alternately with described client, and the HTTP that sets up described concurrent type forever connects.
11. http server according to claim 10 is characterized in that, the described module of setting up specifically is used for
What receive that described client sends sets up HTTP connection request message, comprises the connection type header field in the described HTTP of foundation connection request message, according to described connection type header field, set up with described client between the HTTP of concurrent type forever be connected.
12. a HTML (Hypertext Markup Language) HTTP client is characterized in that, comprising:
Sending module is used for sending the HTTP request message by permanent the connection to server of the HTTP of concurrent type, comprises in the described HTTP request message and handles the identification information header field;
Receiver module is used for forever connecting the http response message that the described server of reception returns by the HTTP of described concurrent type, comprises described processing identification information header field in the described http response message.
13. client according to claim 12 is characterized in that, also comprises setting up module, is used for carrying out alternately with described server, the HTTP that sets up described concurrent type forever connects.
14. client according to claim 13 is characterized in that, the described module of setting up specifically is used for
Set up HTTP connection request message to described server transmission, comprise the connection type header field in the described HTTP of foundation connection request message, so that described server is according to described connection type header field, set up with described client between the HTTP of concurrent type forever be connected.
15. the communication system based on HTML (Hypertext Markup Language) HTTP is characterized in that, comprises client and server, wherein:
Described client is used for sending the HTTP request message by permanent the connection to described server of the HTTP of concurrent type, comprise in the described HTTP request message and handle the identification information header field, and the HTTP by described concurrent type forever connects and receives the http response message that described server returns, and comprises described processing identification information header field in the described http response message;
Described server is used for forever connecting the described HTTP request message that receives described client transmission by the HTTP of described concurrent type, and by permanent connection of the HTTP of described concurrent type returning described http response message to described client.
16. system according to claim 15 is characterized in that,
Described client also is used for carrying out alternately with described server, and the HTTP that sets up described concurrent type forever connects;
Described server also is used for carrying out alternately with described client, and the HTTP that sets up described concurrent type forever connects.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010613201.0A CN102065143B (en) | 2010-12-21 | 2010-12-21 | Communication method and system based on HTTP (hyper Text Transfer Protocol), HTTP server and HTTP client |
| PCT/CN2011/083929 WO2012083806A1 (en) | 2010-12-21 | 2011-12-14 | Http-based communication method and system, http server and http client |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010613201.0A CN102065143B (en) | 2010-12-21 | 2010-12-21 | Communication method and system based on HTTP (hyper Text Transfer Protocol), HTTP server and HTTP client |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102065143A true CN102065143A (en) | 2011-05-18 |
| CN102065143B CN102065143B (en) | 2014-04-30 |
Family
ID=44000242
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010613201.0A Active CN102065143B (en) | 2010-12-21 | 2010-12-21 | Communication method and system based on HTTP (hyper Text Transfer Protocol), HTTP server and HTTP client |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102065143B (en) |
| WO (1) | WO2012083806A1 (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012083806A1 (en) * | 2010-12-21 | 2012-06-28 | 华为技术有限公司 | Http-based communication method and system, http server and http client |
| CN103516673A (en) * | 2012-06-21 | 2014-01-15 | 腾讯科技（深圳）有限公司 | Network data communication method, network data communication system, network data communication client and network data communication server |
| CN104113564A (en) * | 2013-04-17 | 2014-10-22 | 中国移动通信集团公司 | Hyper text transfer protocol connection multiplexing method, device, system, and terminal |
| CN110519775A (en) * | 2018-05-22 | 2019-11-29 | 华为技术有限公司 | Conversation managing method, device and system |
| CN106470221B (en) * | 2015-08-18 | 2019-12-31 | 北京京东尚科信息技术有限公司 | Method for improving inter-process communication coordination efficiency |
| CN112187858A (en) * | 2020-08-24 | 2021-01-05 | 浙江百应科技有限公司 | Method for matching pipeline type http request and response |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1674583A (en) * | 2005-03-24 | 2005-09-28 | 北京北方烽火科技有限公司 | Method for realizing high-speed Le interface based on asynchronous multi-thread |
| CN101083667A (en) * | 2007-07-04 | 2007-12-05 | 华为技术有限公司 | Communication method, system and gateway equipment |
| CN101483599A (en) * | 2009-02-18 | 2009-07-15 | 北京交通大学 | Method for enhancing webpage browsing efficiency based on priority multi-connection |
| US20100268757A1 (en) * | 2009-04-17 | 2010-10-21 | Google Inc. | Pseudo Pipelining of Client Requests |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102065143B (en) * | 2010-12-21 | 2014-04-30 | 华为技术有限公司 | Communication method and system based on HTTP (hyper Text Transfer Protocol), HTTP server and HTTP client |
-
2010
- 2010-12-21 CN CN201010613201.0A patent/CN102065143B/en active Active
-
2011
- 2011-12-14 WO PCT/CN2011/083929 patent/WO2012083806A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1674583A (en) * | 2005-03-24 | 2005-09-28 | 北京北方烽火科技有限公司 | Method for realizing high-speed Le interface based on asynchronous multi-thread |
| CN101083667A (en) * | 2007-07-04 | 2007-12-05 | 华为技术有限公司 | Communication method, system and gateway equipment |
| CN101483599A (en) * | 2009-02-18 | 2009-07-15 | 北京交通大学 | Method for enhancing webpage browsing efficiency based on priority multi-connection |
| US20100268757A1 (en) * | 2009-04-17 | 2010-10-21 | Google Inc. | Pseudo Pipelining of Client Requests |
Non-Patent Citations (1)
| Title |
|---|
| 申王睿: "《硕士论文》", 31 December 2008 * |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012083806A1 (en) * | 2010-12-21 | 2012-06-28 | 华为技术有限公司 | Http-based communication method and system, http server and http client |
| CN103516673A (en) * | 2012-06-21 | 2014-01-15 | 腾讯科技（深圳）有限公司 | Network data communication method, network data communication system, network data communication client and network data communication server |
| CN104113564A (en) * | 2013-04-17 | 2014-10-22 | 中国移动通信集团公司 | Hyper text transfer protocol connection multiplexing method, device, system, and terminal |
| CN106470221B (en) * | 2015-08-18 | 2019-12-31 | 北京京东尚科信息技术有限公司 | Method for improving inter-process communication coordination efficiency |
| CN110519775A (en) * | 2018-05-22 | 2019-11-29 | 华为技术有限公司 | Conversation managing method, device and system |
| CN113993143A (en) * | 2018-05-22 | 2022-01-28 | 华为技术有限公司 | Session management method, device and system |
| US11528770B2 (en) | 2018-05-22 | 2022-12-13 | Huawei Technologies Co., Ltd. | Session management method, apparatus, and system |
| CN112187858A (en) * | 2020-08-24 | 2021-01-05 | 浙江百应科技有限公司 | Method for matching pipeline type http request and response |
| CN112187858B (en) * | 2020-08-24 | 2023-04-18 | 浙江百应科技有限公司 | Method for matching pipeline type http request and response |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102065143B (en) | 2014-04-30 |
| WO2012083806A1 (en) | 2012-06-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102546794B (en) | Method for directly communicating browser client with back-end server as well as gateway and communication system | |
| CN102065143A (en) | Communication method and system based on HTTP (hyper Text Transfer Protocol), HTTP server and HTTP client | |
| CN102272747B (en) | Method and apparatus for managing state information of remote user interface | |
| CN110233881A (en) | Service request processing method, device, equipment and storage medium | |
| US10425253B2 (en) | Inband data gathering with dynamic intermediary route selections | |
| CN101431520A (en) | Method for establishing connection, method for re-orienting connection and correlated equipment | |
| CN103281192B (en) | Method, device and system for retrieving data | |
| CN102098330A (en) | Method, device and system for asynchronous transmission based on json data format | |
| CN102594886B (en) | Method and device for direct communication between browsers, and communication system | |
| CN103533080A (en) | Dispatching method and device for LVS (Linux virtual server) | |
| CN102906727A (en) | Remote application connection sharing | |
| CN107579929B (en) | Method, system and related device for setting reliable connection communication queue pair | |
| CN101986659B (en) | Real-time data transmission method and system | |
| CN106330833A (en) | Communication method based on ICAP (Internet Content Adaptation Protocol), client and server | |
| CN113452778B (en) | Session holding method, device, equipment, system and storage medium | |
| CN103595611B (en) | The realization method and system and equipment of instant messaging application | |
| CN113867958A (en) | Method, device and equipment for pushing task corner mark and readable medium | |
| CN103731424B (en) | A kind of transmission method of network data, apparatus and system | |
| CN102571935B (en) | A kind of method of transfer of data, client, server and system | |
| CN102572735B (en) | The method and apparatus of open mobile communication alliance | |
| CN102165484B (en) | Role-independent context exchange | |
| CN102761780A (en) | Method for obtaining media metadata by intelligent remote controller to | |
| CN103701865A (en) | Data transmission method and system | |
| CN114172958B (en) | Privacy computing node, system, method, device and storage medium | |
| CN103856387B (en) | File retransmission method and system based on instant message client |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |