CN102065143B - 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
- CN102065143B CN102065143B CN201010613201.0A CN201010613201A CN102065143B CN 102065143 B CN102065143 B CN 102065143B CN 201010613201 A CN201010613201 A CN 201010613201A CN 102065143 B CN102065143 B CN 102065143B
- Authority
- CN
- China
- Prior art keywords
- http
- server
- connection
- client
- header field
- 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.)
- Active
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 present invention relates to the communication technology, relates in particular to communication means based on 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 client can be used based on HTML (Hypertext Markup Language) (Hyper Text Transfer Protocol, be called for short HTTP) connect be HTTP connect, 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, be called for short MRFC) between Sr interface.Wherein, above-mentioned HTTP connects can comprise two kinds of connections, and one is that HTTP connects temporarily, and one is that HTTP forever connects.Above-mentioned two kinds of HTTP connect and need to before user end to server be initiated HTTP request, set up, and the former removes after client is returned to http response at server, and the latter is dismounting while sending without any message in the HTTP connection of setting up within a period of time.Therefore, for fear of the HTTP connection of setting up repeating, be connected with dismounting HTTP, above-mentioned interface can be used HTTP forever to connect.The permanent connection of HTTP can comprise two types, and one 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 multiple users to initiate HTTP request by user end to server simultaneously, the former need to set up many HTTP simultaneously and forever connects and could realize the HTTP request of simultaneously processing multiple users with parallel mode, and the latter only needs permanent connection of the HTTP of a streamline type just can realize the HTTP that processes successively multiple users with pipeline system and ask.
In above-mentioned prior art, if use the interface that HTTP connects to use the HTTP of parallel mode forever to connect, need to set up many HTTP simultaneously and forever connect, could realize the HTTP request of simultaneously processing multiple users with parallel mode, increase the complexity that interface configuration administers and maintains; If use the interface that HTTP connects to use the HTTP of streamline type forever to connect, need to carry out order-preserving with http response to HTTP request, reduced the efficiency of interface.
Summary of the invention
The embodiment of the present invention provides communication means based on HTTP and system, http server, HTTP client, the complexity administering and maintaining in order to reduce the interface configuration of using HTTP to connect, and improve the efficiency of using the interface that HTTP connects.
The embodiment of the present invention provides a kind of communication means based on HTTP, comprising:
Server is forever connected and is received the HTTP request message that client sends by the HTTP of concurrent type, comprises and process identification information header field in described HTTP request message;
Described server returns to http response message by permanent connection of HTTP of described concurrent type to described client, comprises described processing identification information header field in described http response message.
The embodiment of the present invention provides the another kind of communication means based on HTTP, comprising:
Client sends HTTP request message by permanent the connection to server of HTTP of concurrent type, comprises and process identification information header field in described HTTP request message;
Described client is forever connected and is received the http response message that described server returns by the HTTP of described concurrent type, comprises described processing identification information header field in described http response message.
The embodiment of the present invention also provides a kind of http server, comprising:
Receiver module, forever connects and receives the HTTP request message that client sends for the HTTP by concurrent type, comprises and process identification information header field in described HTTP request message;
Sending module, for permanent connection of the HTTP by described concurrent type returning to http response message to described client, comprises described processing identification information header field in described http response message.
The embodiment of the present invention also provides a kind of HTTP client, comprising:
Sending module, for permanent connection to server of the HTTP by concurrent type sending HTTP request message, comprises in described HTTP request message and processes identification information header field;
Receiver module, forever connects and receives the http response message that described server returns for the HTTP by described concurrent type, comprises described processing identification information header field in described http response message.
The embodiment of the present invention provides a kind of communication system based on HTML (Hypertext Markup Language) HTTP again, comprises client and server, wherein:
Described client sends HTTP request message for permanent connection to described server of the HTTP by concurrent type, in described HTTP request message, comprise and process identification information header field, and forever connect and receive the http response message that described server returns by the HTTP of described concurrent type, in described http response message, comprise described processing identification information header field;
Described server receives for forever connecting by the HTTP of described concurrent type the described HTTP request message that described client sends, and by permanent connection of HTTP of described concurrent type returning to described http response message to described client.
As shown from the above technical solution, embodiment of the present invention server is forever connected and is received the HTTP request message that comprises processing identification information header field that client sends by the HTTP of concurrent type, make it possible to above-mentioned client, return to the http response message that comprises above-mentioned processing identification information header field by permanent connection of HTTP of above-mentioned concurrent type, realized by the permanent connection of HTTP of a concurrent type and can process multiple HTTP requests, thereby reduced the complexity of using the interface configuration of HTTP connection to administer and maintain, and improved the efficiency of using the interface that HTTP connects.
Accompanying drawing explanation
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, to the accompanying drawing of required use in embodiment or description of the Prior Art be briefly described below, apparently, accompanying drawing in the following describes is some embodiments of the present invention, for those of ordinary skills, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.
The schematic flow sheet of a kind of communication means based on HTTP that Fig. 1 provides for the embodiment of the present invention one;
The schematic flow sheet of the communication means of the another kind that Fig. 2 provides for the embodiment of the present invention two based on HTTP;
The schematic flow sheet of the communication processing method based on HTTP that Fig. 3 provides for the embodiment of the present invention three;
The structural representation of the http server that Fig. 4 provides for the embodiment of the present invention four;
The structural representation of the HTTP client that Fig. 5 provides for the embodiment of the present invention five;
The structural representation of the communication processing system based on HTTP that Fig. 6 provides for the embodiment of the present invention six.
Embodiment
For making object, technical scheme and the advantage of the embodiment of the present invention clearer, below in conjunction with the accompanying drawing in the embodiment of the present invention, technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment in the present invention, those of ordinary skills, not making the every other embodiment obtaining under creative work prerequisite, belong to the scope of protection of the invention.
If use the interface that HTTP connects to use the HTTP of parallel (parallelism) mode forever to connect, need to set up many HTTP forever connects simultaneously, could realize the HTTP request of simultaneously processing multiple users with parallel mode, increase the complexity that interface configuration administers and maintains; If use the interface that HTTP connects to use the HTTP of streamline (pipelining) type forever to connect, need to carry out order-preserving with http response to HTTP request, reduced the efficiency of interface.Therefore, the embodiment of the present invention proposes another HTTP and forever connects, and the HTTP of 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 present invention one, as shown in Figure 1, the communication means based on HTTP of the present embodiment can comprise the following 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, and the http response message that can forever connect for the HTTP of concurrent type is mated with HTTP request message, and 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 server, 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, above-mentioned HTTP response message is specifically as follows success response message, or 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 connecting of HTTP of above-mentioned concurrent type.Particularly, above-mentioned server receives that above-mentioned client sends sets up HTTP connection request message, in the above-mentioned HTTP of foundation connection request message, comprise connection type (Connection-Type) header field, above-mentioned server is according to above-mentioned connection type header field, and the HTTP that sets up the concurrent type between above-mentioned client is forever connected.
Particularly, above-mentioned connection type header field can be used to indicate concurrent type or streamline type, if what user end to server sent sets up the connection type header field indicating concurrent type comprising in HTTP connection request message, the HTTP that sets up concurrent type forever connects, if the connection type header field comprising in HTTP connection request message of setting up that user end to server sends is indicated streamline type, the HTTP that sets up streamline type forever connects.Concrete form can be as follows:
Connection-Type＝″Connection-Type″″:″1#(connection-type)
connection-type＝pipelining|concurrence
Or, above-mentioned connection type header field can also be used to indicate concurrent type, if setting up that user end to server sends comprises this connection type header field in HTTP connection request message, the HTTP that sets up concurrent type forever connects, if setting up in HTTP connection request message that user end to server sends do not comprise this connection type header field, the HTTP that sets up 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 server, 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 to 406 error messages to client, so that client again to this server, initiate not comprise this connection type header field set up HTTP connection request message, according to method of the prior art, the HTTP that sets up streamline type forever connects or the HTTP that sets up many parallel modes forever connects.
Further, when existing multiple users to initiate HTTP request by user end to server simultaneously, the communication means based on HTTP that adopts the present embodiment to provide, can forever connect by the HTTP of a concurrent type of foundation, realize the HTTP request of simultaneously processing multiple users in concurrent mode.
In the present embodiment, server is forever connected and is received the HTTP request message that comprises processing identification information header field that client sends by the HTTP of concurrent type, make it possible to above-mentioned client, return to the http response message that comprises above-mentioned processing identification information header field by permanent connection of HTTP of above-mentioned concurrent type, realized by the permanent connection of HTTP of a concurrent type and can process multiple HTTP requests, thereby reduced the complexity of using the interface configuration of HTTP connection to administer and maintain, and improved the efficiency of the interface that uses HTTP connection.
The schematic flow sheet of the communication means of the another kind that Fig. 2 provides for the embodiment of the present invention two based on HTTP, as shown in Figure 2, the communication means based on HTTP of the present embodiment can comprise the following steps:
Step 201, client send HTTP request message by permanent the connection to server of HTTP of concurrent type, comprise and process identification information (Transaction-Id) header field in above-mentioned HTTP request message;
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, and the http response message that can forever connect for the HTTP of concurrent type is mated with HTTP request message, and 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 server, this agent equipment needs to support the above-mentioned processing identification information of transparent transmission header field.
Step 202, above-mentioned client are forever connected and are received the http response message that above-mentioned server returns by the HTTP of above-mentioned concurrent type, comprise above-mentioned processing identification information header field in above-mentioned HTTP response message.
Http response message wherein can include but not limited to GET response message, OPTIONS response message.
Particularly, above-mentioned HTTP response message is specifically as follows success response message, or 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 connecting of HTTP of above-mentioned concurrent type.Particularly, above-mentioned client sends and sets up HTTP connection request message to above-mentioned server, in the above-mentioned HTTP of foundation connection request message, comprise connection type (Connection-Type) header field, so that above-mentioned server is according to above-mentioned connection type header field, the HTTP that sets up the concurrent type between above-mentioned client is forever connected.
Particularly, above-mentioned connection type header field can be used to indicate concurrent type or streamline type, if what user end to server sent sets up the connection type header field indicating concurrent type comprising in HTTP connection request message, the HTTP that sets up concurrent type forever connects, if the connection type header field comprising in HTTP connection request message of setting up that user end to server sends is indicated streamline type, the HTTP that sets up streamline type forever connects.Concrete form can be as follows:
Connection-Type＝″Connection-Type″″:″1#(connection-type)
connection-type＝pipelining|concurrence
Or, above-mentioned connection type header field can also be used to indicate concurrent type, if setting up that user end to server sends comprises this connection type header field in HTTP connection request message, the HTTP that sets up concurrent type forever connects, if setting up in HTTP connection request message that user end to server sends do not comprise this connection type header field, the HTTP that sets up 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 server, 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 to 406 error messages to client, so that client again to this server, initiate not comprise this connection type header field set up HTTP connection request message, according to method of the prior art, the HTTP that sets up streamline type forever connects or the HTTP that sets up many parallel modes forever connects.
Further, when existing multiple users to initiate HTTP request by user end to server simultaneously, the communication means based on HTTP that adopts the present embodiment to provide, can forever connect by the HTTP of a concurrent type of foundation, realize the HTTP request of simultaneously processing multiple users in concurrent mode.
In the present embodiment, client was sent and is comprised the HTTP request message of processing identification information header field by permanent the connection to server of HTTP of concurrent type, make it possible to forever 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 by the permanent connection of HTTP of a concurrent type and can process multiple HTTP requests, thereby reduced the complexity of using the interface configuration of HTTP connection to administer and maintain, and improved the efficiency of the interface that uses HTTP connection.
Take IMS as example, the technical scheme of the invention described above embodiment mono-and the invention described above embodiment bis-is elaborated.The schematic flow sheet of the communication processing method based on HTTP that Fig. 3 provides for the embodiment of the present invention three, as shown in Figure 3, the communication processing method based on HTTP of the present embodiment can comprise the following steps:
For example:
For example:
In the present embodiment, MRFC was sent and is comprised the HTTP request message of processing identification information header field by permanent the connection to AS of HTTP of concurrent type, make AS to MRFC, to return to the http response message that comprises above-mentioned processing identification information header field by permanent connection of the HTTP of above-mentioned concurrent type, realized by the permanent connection of HTTP of a concurrent type and can process multiple HTTP requests, thereby reduced the complexity of Sr interface configuration management and maintenance, and improved the efficiency of Sr interface.
It should be noted that: for aforesaid each embodiment of the method, for simple description, therefore it is all expressed as to a series of combination of actions, but those skilled in the art should know, the present invention is not subject 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 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, in certain embodiment, there is no the part of detailed description, 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 present invention four, as shown in Figure 4, the http server of the present embodiment can comprise receiver module 41 and sending module 42.Wherein, receiver module 41 is forever connected and is received the HTTP request message that client sends by the HTTP of concurrent type, in above-mentioned HTTP request message, comprise and process identification information header field, sending module 42 returns to http response message by permanent connection of HTTP of above-mentioned concurrent type to above-mentioned client, comprises above-mentioned processing identification information header field in above-mentioned HTTP response message.
The http server that in the invention described above embodiment mono-, in server, the embodiment of the present invention three, the function of AS all can be provided by the embodiment of the present invention is realized.
In the present embodiment, receiver module is forever connected and is received the HTTP request message that comprises processing identification information header field that client sends by the HTTP of concurrent type, make sending module to above-mentioned client, to return to the http response message that comprises above-mentioned processing identification information header field by permanent connection of the HTTP of above-mentioned concurrent type, realized by the permanent connection of HTTP of a concurrent type and can process multiple HTTP requests, thereby reduced the complexity of using the interface configuration of HTTP connection to administer and maintain, and improved the efficiency of the interface that uses HTTP connection.
Further, the http server of the present embodiment can further include sets up module 43, and for carrying out alternately with above-mentioned client, the HTTP that sets up above-mentioned concurrent type forever connects.Particularly, set up module 43 and specifically can set up HTTP connection request message for what receive that above-mentioned client sends, in the above-mentioned HTTP of foundation connection request message, comprise connection type header field, according to above-mentioned connection type header field, the HTTP that sets up the concurrent type between above-mentioned client is forever connected.
The structural representation of the HTTP client that Fig. 5 provides for the embodiment of the present invention five, as shown in Figure 5, the HTTP client of the present embodiment can comprise sending module 51 and receiver module 52.Wherein, sending module 51 sends HTTP request message by permanent the connection to server of HTTP of concurrent type, in above-mentioned HTTP request message, comprise and process identification information header field, receiver module 52 is forever connected and is received the http response message that above-mentioned server returns by the HTTP of above-mentioned concurrent type, comprises above-mentioned processing identification information header field in above-mentioned HTTP response message.
The HTTP client that in the invention described above embodiment bis-, in client, the embodiment of the present invention three, the function of MRFC all can be provided by the embodiment of the present invention realizes.
In the present embodiment, sending module was sent and is comprised the HTTP request message of processing identification information header field by permanent the connection to server of HTTP of concurrent type, make receiver module forever to connect and to 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 by the permanent connection of HTTP of a concurrent type and can process multiple HTTP requests, thereby reduced the complexity of using the interface configuration of HTTP connection to administer and maintain, and improved the efficiency of the interface that uses HTTP connection.
Further, the HTTP client of the present embodiment can further include sets up module 53, and for carrying out alternately with above-mentioned server, the HTTP that sets up above-mentioned concurrent type forever connects.Particularly, set up module 53 and specifically can set up HTTP connection request message for upwards stating server transmission, in the above-mentioned HTTP of foundation connection request message, comprise connection type header field, so that above-mentioned server is according to above-mentioned connection type header field, the HTTP that sets up the concurrent type between above-mentioned client is forever connected.
The structural representation of the communication processing system based on HTTP that Fig. 6 provides for the embodiment of the present invention six, as shown in Figure 6, the communication processing system based on HTTP of the present embodiment can comprise client 61 and server 62, wherein:
In the present embodiment, server is forever connected and is received the HTTP request message that comprises processing identification information header field that client sends by the HTTP of concurrent type, make it possible to above-mentioned client, return to the http response message that comprises above-mentioned processing identification information header field by permanent connection of HTTP of above-mentioned concurrent type, realized by the permanent connection of HTTP of a concurrent type and can process multiple HTTP requests, thereby reduced the complexity of using the interface configuration of HTTP connection to administer and maintain, and improved the efficiency of the interface that uses 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 complete by the relevant hardware of program command, aforesaid program can be stored in a computer read/write memory medium, this program, when carrying out, is carried out the step that comprises said method embodiment; And aforesaid storage medium comprises: various media that can be program code stored such as ROM, RAM, magnetic disc or CDs.
Finally it should be noted that: above embodiment only, in order to technical scheme of the present invention to be described, is not intended to limit; Although the present invention is had been described in detail with reference to previous embodiment, those of ordinary skill in the art is to be understood that: its technical scheme that still can record aforementioned each embodiment is modified, or part technical characterictic is wherein equal to replacement; And these modifications or replacement do not make the essence of appropriate technical solution depart 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 is forever connected and is received the HTTP request message that client sends by the HTTP of concurrent type, comprises and process identification information header field in described HTTP request message;
Described server returns to http response message by permanent connection of HTTP of described concurrent type to described client, comprises described processing identification information header field in described http response message;
Wherein, described server is processed multiple described HTTP request messages by the permanent connection of HTTP of a described concurrent type simultaneously, and described processing identification information header field mates for described http response message and described HTTP request 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, in the described HTTP of foundation connection request message, comprises connection type header field;
Described server is according to described connection type header field, and the HTTP that sets up the concurrent type between described client is forever connected.
4. according to the method described in the arbitrary claim of claim 1～3, it is characterized in that permanent the connection for the Sr interface between IP Multimedia System IMS client and server of HTTP of described concurrent type.
5. the communication means based on HTML (Hypertext Markup Language) HTTP, is characterized in that, comprising:
Client sends HTTP request message by permanent the connection to server of HTTP of concurrent type, and in described HTTP request message, comprise and process identification information header field;
Described client is forever connected and is received the http response message that described server returns by the HTTP of described concurrent type, comprises described processing identification information header field in described http response message;
Wherein, described client is processed multiple described HTTP request messages by the permanent connection of HTTP of a described concurrent type simultaneously, and described processing identification information header field mates for described http response message and described HTTP request 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 and sets up HTTP connection request message to described server, in the described HTTP of foundation connection request message, comprise connection type header field, so that described server is according to described connection type header field, the HTTP that sets up the concurrent type between described client is forever connected.
8. according to the method described in the arbitrary claim of claim 5～7, it is characterized in that permanent the connection for the Sr interface between IP Multimedia System IMS client and server of HTTP of described concurrent type.
9. a HTML (Hypertext Markup Language) http server, is characterized in that, described http server is processed multiple HTTP request messages by the permanent connection of HTTP of a concurrent type simultaneously, and described http server comprises:
Receiver module, forever connects and receives the HTTP request message that client sends for the HTTP by concurrent type, comprises and process identification information header field in described HTTP request message;
Sending module, for permanent connection of the HTTP by described concurrent type returning to http response message to described client, in described http response message, comprise described processing identification information header field, described processing identification information header field mates for described http response message and described HTTP request message.
10. http server according to claim 9, is characterized in that, also comprises and sets up module, and for carrying out alternately with described client, the HTTP that sets up described concurrent type forever connects.
11. http servers according to claim 10, is characterized in that, described set up module specifically for
What receive that described client sends sets up HTTP connection request message, in the described HTTP of foundation connection request message, comprises connection type header field, and according to described connection type header field, the HTTP that sets up the concurrent type between described client is forever connected.
12. 1 kinds of HTML (Hypertext Markup Language) HTTP clients, is characterized in that, described client is processed multiple HTTP request messages by the permanent connection of HTTP of a concurrent type simultaneously, and described client comprises:
Sending module, for permanent connection to server of the HTTP by concurrent type sending HTTP request message, comprises in described HTTP request message and processes identification information header field;
Receiver module, for forever connecting by the HTTP of described concurrent type, receive the http response message that described server returns, in described http response message, comprise described processing identification information header field, described processing identification information header field mates for described http response message and described HTTP request message.
13. clients according to claim 12, is characterized in that, also comprise and set up module, and for carrying out alternately with described server, the HTTP that sets up described concurrent type forever connects.
14. clients according to claim 13, is characterized in that, described set up module specifically for
To described server, send and set up HTTP connection request message, in the described HTTP of foundation connection request message, comprise connection type header field, so that described server is according to described connection type header field, the HTTP that sets up the concurrent type between described client is forever connected.
15. 1 kinds of communication systems based on HTML (Hypertext Markup Language) HTTP, is characterized in that, comprise client and server, and described server and described client are processed multiple HTTP request messages by the permanent connection of HTTP of a concurrent type simultaneously, wherein:
Described client sends HTTP request message for permanent connection to described server of the HTTP by concurrent type, in described HTTP request message, comprise and process identification information header field, and forever connect and receive the http response message that described server returns by the HTTP of described concurrent type, in described http response message, comprise described processing identification information header field;
Described server receives for forever connecting by the HTTP of described concurrent type the described HTTP request message that described client sends, and permanent connection of the HTTP by described concurrent type returning to described http response message to described client, described processing identification information header field mates for described http response message and described HTTP request message.
16. systems according to claim 15, is characterized in that,
Described client is also for carrying out alternately with described server, and the HTTP that sets up described concurrent type forever connects;
Described server is also 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 CN102065143A (en) | 2011-05-18 |
| CN102065143B true 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) |
Families Citing this family (6)
| 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 |
| 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 |
| CN113993143A (en) * | 2018-05-22 | 2022-01-28 | 华为技术有限公司 | Session management method, device and system |
| CN112187858B (en) * | 2020-08-24 | 2023-04-18 | 浙江百应科技有限公司 | Method for matching pipeline type http request and response |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101483599A (en) * | 2009-02-18 | 2009-07-15 | 北京交通大学 | Method for enhancing webpage browsing efficiency based on priority multi-connection |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100539589C (en) * | 2005-03-24 | 2009-09-09 | 北京北方烽火科技有限公司 | A kind of high speed Le interface implementation method based on asynchronous multithreading |
| CN101083667A (en) * | 2007-07-04 | 2007-12-05 | 华为技术有限公司 | Communication method, system and gateway equipment |
| US20100268757A1 (en) * | 2009-04-17 | 2010-10-21 | Google Inc. | Pseudo Pipelining of Client Requests |
| 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 (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101483599A (en) * | 2009-02-18 | 2009-07-15 | 北京交通大学 | Method for enhancing webpage browsing efficiency based on priority multi-connection |
Non-Patent Citations (1)
| Title |
|---|
| 申王睿."SCTP多流优先级的研究与实现".《硕士论文》.2008,第5章. |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2012083806A1 (en) | 2012-06-28 |
| CN102065143A (en) | 2011-05-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102065143B (en) | Communication method and system based on HTTP (hyper Text Transfer Protocol), HTTP server and HTTP client | |
| CN102546794B (en) | Method for directly communicating browser client with back-end server as well as gateway and communication system | |
| CN105208043A (en) | Outer network agent module, inner network agent module and data transmitting method and system | |
| CN104717133A (en) | Distributed message push system and method | |
| CN101193089A (en) | Stateful session system and its realization method | |
| CN103139051A (en) | Instant messaging communication method based on Websocket protocol | |
| WO2012000228A1 (en) | Method for group communication implemented on common web page | |
| CN101431520A (en) | Method for establishing connection, method for re-orienting connection and correlated equipment | |
| CN104580097A (en) | Data processing method, device and system | |
| CN103281192B (en) | Method, device and system for retrieving data | |
| CN102098330A (en) | Method, device and system for asynchronous transmission based on json data format | |
| CN112612985A (en) | Websocket-based multi-user and multi-type message pushing system and method | |
| CN107342934A (en) | A kind of mixed mode Mobile solution real-time messages method for pushing and system based on WebSocket | |
| US20180035143A1 (en) | Popping-screen push system and method | |
| US10320951B2 (en) | Systems and methods for establishing a virtual local area network | |
| CN104052746A (en) | Heterogeneous application single sign-on system and method | |
| CN102594886B (en) | Method and device for direct communication between browsers, and communication system | |
| CN105025047A (en) | Cloud desktop pushing method, system and pushing end and receiving end | |
| CN113938516A (en) | Method and system for synchronously realizing transaction processing of heterogeneous system | |
| CN104539510A (en) | Multi-protocol-based information pushing system and method | |
| CN101986659B (en) | Real-time data transmission method and system | |
| CN106330833A (en) | Communication method based on ICAP (Internet Content Adaptation Protocol), client and server | |
| CN101282339A (en) | Capability negotiation method for flow medium system, data transmission method as well as related equipment | |
| CN113867958A (en) | Method, device and equipment for pushing task corner mark and readable medium | |
| CN103595611B (en) | The realization method and system and equipment of instant messaging application |
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 |