CN101635744B - Method and system for transmitting data and relative equipment - Google Patents
Method and system for transmitting data and relative equipment Download PDFInfo
- Publication number
- CN101635744B CN101635744B CN200910167149A CN200910167149A CN101635744B CN 101635744 B CN101635744 B CN 101635744B CN 200910167149 A CN200910167149 A CN 200910167149A CN 200910167149 A CN200910167149 A CN 200910167149A CN 101635744 B CN101635744 B CN 101635744B
- Authority
- CN
- China
- Prior art keywords
- subpackage
- data
- data subpackage
- sent
- web service
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method and a system for transmitting data and relative equipment, which are applied to the field of Web service for realizing the high-efficient interaction of a large amount of data. The method comprises the following steps: intercepting Web service request information sent by a request party and creating a channel object by an interceptor, then obtaining a result set by a service logic entity, and sub-packaging the result set to obtain N data sub-packets; sending the previous (N-1)th data sub-packets to a Response Handler Chain through the channel object, and sending the data sub-packets to the request party through the Response Handler Chain; sending the Nth data sub-packets to the Response Handler Chain, and sending the data sub-packets to the request party through the Response Handler Chain. The invention can realize the high-efficient interaction of a large amount of data.
Description
Technical field
The present invention relates to the communications field, relate in particular to a kind of data transmission method and data transmission system and relevant device.
Background technology
Network service (Web Service) mainly is a kind of interface that can exchange each other, share and propose for the information that makes between the isolated originally website.
Web Service is employed to be that unified, open standard is gone up in the Internet (Internet); Like HTTP (HTTP; Hyper Texture Transport Protocol), extending mark language (XML; EXtensible Markup Language), Simple Object Access Protocol (SOAP; Simple Object AccessProtocol), web services definition language (WSDL, Web Services Description Language) etc., so Web Service can use in the environment (for example Windows or Linux) of any these standards of support.The design object of Web Service is exactly simplicity and autgmentability, and this helps the interoperability between a large amount of isomery programs and the platform, thereby makes the application program of existence can be by user capture widely.
Generally speaking, Web Service can be divided into several logical levels: transport layer, message layer and service definition layer; Wherein, Transport layer mainly is responsible for the physical connection of bottom, and message layer has defined message exchange pattern (MEP, Message exchange patterns) and soap message form.The service definition layer has then been described the business interface and other relevant information of Web Service service, like safety, and service quality (QoS, Quality of Service) etc.
MEP defined use Web Service come interactive information the pattern that must observe; One of scene that produces new MEP is exactly the situation that mutual both sides need the big data quantity exchange; Only, can not satisfy the big data quantity switching requirement through the simple MEP of one-time request one secondary response.
Such as being directed against one-time request; Response party is returned the data that reach several megabits; And the requesting party once can not handle these data, thereby the requesting party hopes to carry out certain Flow Control, thus the rhythm of control return data amount; What a kind of data transmission method mainly adopted in the prior art is iteration pattern, and concise and to the point process is following:
When response party confirms that quantity surpasses the quantity of expecting as a result; Just earlier the result is carried out subpackage; Create an iteration sub-instance afterwards, stem branch result is quoted with this iteration return to the requesting party together then, this iteration sub-instance will keep the average information relevant with this request;
The requesting party receives after stem branch result and iteration; Promptly know in addition subsequent result, if the requesting party also need obtain subsequent result, then according to this iteration once more to the response party initiation request; For example send GET NEXT to response party, then response party can be sent follow-up result successively.
The inventor is in realizing process of the present invention; Find in the above-mentioned prior art; Response party need be preserved a large amount of average informations, and for example response party need be preserved current how many results that sent, and could when the GET NEXT request of receiving the requesting party, send follow-up result; Therefore increase the expense of response party, influenced the efficient of transfer of data.
Summary of the invention
The embodiment of the invention provides a kind of data transmission method and data transmission system and equipment, to realize big data quantity exchange efficiently.
The data transmission method that the embodiment of the invention provides; Be applied to the network Web service; Comprise: after interceptor was intercepted and captured the Web service request message of requesting party's transmission and created the passage object, service logic entity obtained results set according to said Web service request message; When confirming as one-time request multiple response pattern, said results set is carried out the subpackage processing obtain N data subpackage; Preceding N-1 data subpackage in said N the data subpackage sent to response process chain Response Handler Chain through said passage object, and said preceding N-1 data subpackage is sent to described request side through said Response Handler Chain; N data subpackage in said N the data subpackage sent to said Response Handler Chain, and said N data subpackage is sent to described request side through said Response Handler Chain.
The data transmission method that the embodiment of the invention provides comprises: intercept and capture the network Web service request message of requesting party's transmission and create the passage object; Intercept and capture the results set that service logic entity is returned, said results set is obtained according to said Web service request message by service logic entity; When confirming as one-time request multiple response pattern, results set is carried out the subpackage processing obtain N data subpackage; Preceding N-1 data subpackage in said N the data subpackage sent to response process chain ResponseHandler Chain through said passage object, and said preceding N-1 data subpackage is sent to described request side through said Response Handler Chain; N data subpackage in said N the data subpackage sent to said ResponseHandler Chain, and said N data subpackage is sent to described request side through said Response Handler Chain.
The data transmission system that the embodiment of the invention provides comprises: interceptor, be used to intercept and capture the network Web service request message that the requesting party sends, and create the passage object; Service logic entity; Be used for obtaining results set according to the Web service request message that receives; When confirming as one-time request multiple response pattern; Said results set is carried out the subpackage processing obtain N data subpackage, preceding N-1 data subpackage in said N the data subpackage sent to response process chain Response Handler Chain through said passage object, said preceding N-1 data subpackage is sent to described request side through said Response Handler Chain; N data subpackage in said N the data subpackage sent to said Response Handler Chain, and said N data subpackage is sent to described request side through said Response Handler Chain.
The data transmission system that the embodiment of the invention provides; Comprise: interceptor; Be used to intercept and capture the Web service request message that the requesting party sends, create the passage object, intercept and capture the results set that service logic entity is sent; When confirming as one-time request multiple response pattern; Said results set is carried out subpackage obtain N data subpackage, preceding N-1 data subpackage in said N the data subpackage sent to response process chain Response Handler Chain through said passage object, said preceding N-1 data subpackage is sent to described request side through said ResponseHandler Chain; N data subpackage in said N the data subpackage sent to said Response Handler Chain, and said N data subpackage is sent to described request side through said ResponseHandler Chain; Service logic entity is used for obtaining the corresponding results set according to the Web service request message that receives, and returns said results set.
The service logic entity that the embodiment of the invention provides comprises: acquiring unit is used to obtain the network Web service request message that the requesting party sends; The business logic processing unit is used for obtaining results set according to said Web service request message; The first subpackage unit when being used to confirm as one-time request multiple response pattern, carrying out the subpackage processing to said results set and obtains N data subpackage; First transmission unit; Be used for preceding N-1 data subpackage of said N data subpackage sent to response process chain Response Handler Chain through said passage object, said preceding N-1 data subpackage is sent to described request side through said ResponseHandler Chain; N data subpackage in said N the data subpackage sent to said Response Handler Chain, and said N data subpackage is sent to described request side through said ResponseHandler Chain.
The interceptor that the embodiment of the invention provides comprises: intercept and capture the unit, be used to intercept and capture the network Web service request message of requesting party's transmission and intercept and capture the results set that service logic entity is returned; Create the unit, be used to create the passage object; The second subpackage unit is used for when confirming as one-time request multiple response pattern, results set is carried out the subpackage processing obtain N data subpackage; Second transmission unit; Be used for preceding N-1 data subpackage of said N data subpackage sent to response process chain ResponseHandler Chain through said passage object, said preceding N-1 data subpackage is sent to described request side through said Response Handler Chain; N data subpackage in said N the data subpackage sent to said ResponseHandler Chain, and said N data subpackage is sent to described request side through said Response Handler Chain.
Can find out that from above technical scheme the embodiment of the invention has the following advantages:
In the embodiment of the invention; Service logic entity can be carried out subpackage to results set after getting access to results set, and directly the data subpackage that obtains is sent to the requesting party; And need not to wait for that the requesting party asks subsequent result once more; Therefore service logic entity need not to preserve the average information of transfer of data, thereby has reduced the expense of service logic entity, has realized the ability of big data quantity exchange efficiently.
Description of drawings
Fig. 1 is embodiment sketch map of data transmission method in the embodiment of the invention;
Fig. 2 is another embodiment sketch map of data transmission method in the embodiment of the invention;
Fig. 3 is a data transmission method embodiment sketch map again in the embodiment of the invention;
Fig. 4 is a data transmission system embodiment sketch map in the embodiment of the invention;
Fig. 5 is a service logic entity embodiment sketch map in the embodiment of the invention;
Fig. 6 is an interceptor embodiment sketch map in the embodiment of the invention.
Embodiment
The embodiment of the invention provides a kind of data transmission method and data transmission system and relevant device, is applied to Web service, is used to realize that big data quantity is mutual efficiently.
See also Fig. 1, the data transmission method in the embodiment of the invention one embodiment comprises:
101, service logic entity is obtained the Web service request message that the requesting party sends;
In the present embodiment; When the requesting party sends the Web service request message to service end; This Web service request message can pass through the communication aspect; Get into the Request Processing chain (Request Handler Chain) of JAVA network service application interface (JAXWS, Java APIfor XML Web Services) definition.
, in the process that the service logic entity of service end is sent, can be intercepted and captured by interceptor at this Web service request message, interceptor can extract the current JAXWS operation context that calls.
Interceptor is after intercepting and capturing the Web service request message; Interceptor can be created with current and call corresponding passage object; And the JAXWS that gets access to operation context is stored in the passage object, and with the passage object storage in current thread local storage of calling.
Need to prove; In the present embodiment, the Web service request message that service logic entity gets access to can get access to from interceptor, also can directly get access to from the requesting party; Be that interceptor is after the Web service request message that receives requesting party's transmission; Can this Web service request message is temporary, the implementation in the establishment tunnel of the line correlation of going forward side by side is forwarded to service logic entity with this Web service request message afterwards again; Be that service logic entity can get access to this Web service request message from interceptor; Perhaps this interceptor can directly copy a Web service request message after receiving the Web service request message that the requesting party sends, and the implementation in the establishment tunnel of being correlated with according to the Web service request message of this copy; And directly take the mode of transparent transmission to be sent to service logic entity to original Web service request message, then service logic entity can directly get access to this Web service request message from the requesting party.
102, service logic entity is obtained results set according to the Web service request message;
In the present embodiment; After interceptor has been created the passage object; Service logic entity can be obtained corresponding results set according to the Web service request message that in step 101, gets access to; Be the content of requestor requests, concrete acquisition process is those skilled in the art's a common practise, does not limit here.
103, when service logic entity is confirmed as one-time request multiple response pattern, results set is carried out the subpackage processing obtain N data subpackage;
Specifically can be that service logic entity is confirmed as one-time request multiple response pattern according to said Web service request message and said results set;
After service logic entity gets access to results set; Then can judge whether to be one-time request response modes repeatedly according to Web service request message and this results set; If; Then can carry out the subpackage processing to this results set according to the parameter in the Web service request message and obtain N data subpackage, the process of concrete subpackage will be carried out detailed description in the subsequent implementation example.
Need explanation, specifically can judge whether to be one-time request response modes repeatedly according to the message header information in results set and the Web service request message or message body information.
104, service logic entity is sent through the passage object preceding N-1 data subpackage to response process chain Response Handler Chain, and preceding N-1 data subpackage is sent to described request side through the response process chain;
After having accomplished the branch package operation; Obtain N data subpackage; Service logic entity is sent to the passage object with preceding N-1 data subpackage wherein; By this passage object this N-1 data subpackage is sent to the response process chain again, finally this N-1 data subpackage is sent to the requesting party by this response process chain.
105, service logic entity is sent N data subpackage to the response process chain, and N data subpackage is sent to the requesting party through the response process chain.
After the transmission of having accomplished preceding N-1 data subpackage; Service logic entity is with last data subpackage; I.e. N data subpackage sent according to normal echo plex mode, promptly not through the passage object; But service logic entity is directly sent this N data subpackage to the response process chain, finally by this response process chain this N data subpackage is sent to the requesting party.
Need to prove that N is the positive integer greater than 1.
It is thus clear that in the embodiment of the invention, service logic entity is after getting access to results set; Can carry out subpackage to results set; And directly the data subpackage that obtains is sent to the requesting party, and need not to wait for that the requesting party asks subsequent result once more, so service logic entity need not to preserve the average information of transfer of data; Thereby reduced the expense of service logic entity, realized the ability of big data quantity exchange efficiently.
Angle from service logic entity is described the data transmission method the embodiment of the invention above; For ease of understanding; From interceptor and the mutual angle of service logic entity the data transmission method the embodiment of the invention is described in detail below; See also Fig. 2, another embodiment of the data transmission method in the embodiment of the invention comprises:
201, interceptor is intercepted and captured the Web service request message that the requesting party sends;
In the present embodiment, when the requesting party sent the Web service request message to service end, this Web service request message can pass through the communication aspect, got into the Request Handler Chain of JAXWS definition.
Pass through Request Handler Chain in the process that the service logic entity of service end is sent at this Web service request message; Intercepted and captured by interceptor; Interceptor can extract the current JAXWS operation context that calls; Concrete JAXWS moves context and extracts the current JAXWS that calls and move the common practise that contextual process is those skilled in the art, does not limit here.
Describe with the type of message of soap message, it is understandable that, in practical application, equally also possibly use other type of message, specifically do not limit here as transmission.
The message header of the soap message in the present embodiment (Header) is used to realize requesting party and the service end information interaction on protocol level, and this message header specifically can comprise following contents:
(1) request type (Request Type): be used to define the response mode of requesting party's expectation, such as being iteration response or one-time request multiple response mode, or one-time request one secondary response;
(2) association identification (CorrelationID): be used to realize produced unique identification symbol that request message and response message are mated each other by the requesting party, service end will all will be carried this identifier in the message of each response;
(3) maximum amount of data (Max Number): the data volume that in a response message, comprises at most of expression requesting party expectation;
(4) message sum (Total): the information that the first response message that returns of service end carries is used to tell what response messages the requesting party will have return altogether;
(5) current sequence number (Current Sequence No): the sequence number that is used to represent the message of current response;
(6) finish sign (Finished): being used to indicate current response message is a last response message, and the request response process finishes.
The requesting party carries Request Type in the Web service request message that sends, CorrelationID and Max Number are used to echo plex mode, association identification and the data volume of once returning at most of representing that the requesting party is desired.
202, interceptor is created the passage object;
Interceptor is after intercepting and capturing the Web service request message; Interceptor can be created with current and call corresponding passage object; And the JAXWS that gets access in the step 201 operation context is stored in the passage object, and with the passage object storage in current thread local storage of calling.
In the present embodiment; The process of whole transfer of data is all implemented by same thread; So the passage object storage can be moved JAXWS critical data and current thread bindings such as context in the thread local storage; Therefore no matter can from the thread local storage, get access to these critical datas at any time, thereby can accomplish transfer of data follow-up in the present embodiment in any moment of this thread enforcement transfer of data.
203, service logic entity is obtained results set according to the Web service request message;
In the present embodiment; Service logic entity can be obtained corresponding results set, the i.e. content of requestor requests according to this message after the Web service request message that gets access to requesting party's transmission; Concrete acquisition process is those skilled in the art's a common practise, does not limit here.
Need to prove that in the present embodiment, the process that service logic entity is obtained the Web service request message equally can be the same with the mode described among the aforementioned embodiment shown in Figure 1, repeats no more here.
204, service logic entity judges whether to be one-time request multiple response pattern, if then execution in step 206, if not, then execution in step 205;
In the present embodiment; After service logic entity is getting access to results set; Can judge whether to be one-time request multiple response pattern according to this results set and Web service request message (specifically can be Web service request message header), concrete deterministic process can for:
Service logic entity judges whether the Request Type in the message header information of Web service request message is designated as one-time request multiple response pattern; If; Whether the data volume that then continues the judged result set is greater than the Max Number in the Web service request message; If greater than, then confirm as one-time request multiple response pattern.
It is understandable that; The deterministic process of foregoing description is merely an instantiation; In practical application, can also adopt other deterministic process equally, (in other words the data volume of for example confirming results set when service logic entity just is defaulted as one-time request multiple response pattern during greater than the Max Number in the Web service request message; Promptly start one-time request multiple response pattern), concrete more deterministic process does not limit here.
205, carry out other handling processes;
If the Request Type in the message header information of Web service request message is not an indication one-time request multiple response pattern; Or the data volume of results set is less than the Max Number in the message header information of Web service request message; Then service logic entity confirms not to be one-time request multiple response pattern; This moment, service logic entity can adopt other handling process to handle, and for example carried out the iteration response, or one-time request one secondary response; Detailed process is those skilled in the art's a common practise, does not limit here.
206, service logic entity is carried out subpackage according to the maximum amount of data parameter in the Web service request message to results set;
When service logic entity is confirmed as one-time request multiple response pattern; Service logic entity is carried out subpackage according to the Max Number in the message header information of Web service request message to results set; The process of concrete subpackage can adopt average subpackage; Or subpackage at random, or other branch packet procedures, as long as make the data volume of each data subpackage all be less than or equal to Max Number.
After service logic entity is accomplished subpackage to results set, obtain N data subpackage, service logic entity all is encapsulated as an independently soap message with each data subpackage again, promptly obtains N soap message:
Include Request Type in the message header of first soap message; CorrelationID, Total and Current Sequence No, wherein; Request Type is designated as the one-time request multiple response; CorrelationID corresponding with the CorrelationID in the Web service request message (specifically can for identical), Total representes the quantity (being N) of soap message altogether, Current Sequence No representes the sequence number (being 1) of current soap message;
Include Request Type in the message header of second middle soap message to the N-1 soap message, CorrelationID and Current Sequence No, the content implication in the message header of concrete implication and first soap message is similar;
Include Request Type in the message header of N (being last) soap message; CorrelationID; Current Sequence No and Finished; Wherein, Request Type is designated as the one-time request multiple response, CorrelationID corresponding with the CorrelationID in the Web service request message (specifically can for identical); Current Sequence No representes the sequence number (being N) of current soap message, and all data subpackages of Finished ecbatic set have all been sent and finished.
207, service logic entity is sent through the passage object preceding N-1 data subpackage to the response process chain, and preceding N-1 data subpackage is sent to described request side through the response process chain;
After service logic entity obtains N soap message; Service logic entity can extract the passage object from the local storage of current thread; Preceding N-1 soap message in N the soap message is sent to the passage object; The JAXWS operation context that adds in this passage object extraction step 202 afterwards; And move from this JAXWS and to obtain quoting of Response Handler Chain the contextual internal damping, this N-1 soap message is sent to this Response Handler Chain, and N-1 soap message is sent to the requesting party by this Response Handler Chain.
208, service logic entity is sent N data subpackage to identical response process chain, and N data subpackage is sent to the requesting party through this identical response process chain.
After service logic entity has been sent a preceding N-1 soap message; Last (promptly N) soap message adopts normal echo plex mode to return; Promptly directly this N soap message mail to Response Handler Chain, be back to the requesting party by Response Handler Chain.
Need to prove; In the present embodiment, this N soap message can be intercepted and captured by interceptor before arriving Response HandlerChain, and this moment, interceptor confirmed that according to the message header of this N soap message this soap message is last data subpackage of results set; Then interceptor is carried out relevant cleaning work; Remove the current relevant information of calling, wherein comprise the passage object at least, can further include the passage object and quote etc. JAXWS operation is contextual.
Interceptor has been accomplished after the cleaning work, can this N soap message be sent to ResponseHandler Chain, by Response Handler Chain this N soap message is mail to the requesting party, thereby accomplishes current calling.
Need to prove; The requesting party is after receiving soap message; Can confirm the response message which request message these soap messages are according to the CorrelationID in the message header of soap message; And; The requesting party can also determine whether to receive whole soap messages according to Total in the message header of soap message and CurrentSequence No, when finding not receive whole soap messages, and can also be according to Current Sequence No to the service end request repeat.
It is thus clear that in the present embodiment, service logic entity is after getting access to results set; Can carry out subpackage to the result; And directly the data subpackage that obtains is sent to the requesting party, and promptly can realize returning and Flow Control of big data quantity, reach identical effect with the data transmission procedure of iterative manner of the prior art; And need not to wait for that the requesting party asks subsequent result once more in the present embodiment simultaneously; Therefore service logic entity need not to preserve the average information of transfer of data, thereby has reduced the expense of service logic entity, has realized that big data quantity is mutual efficiently;
Secondly; In the present embodiment; Because when service logic entity was sent last data subpackage, interceptor can be removed the current relevant information of calling automatically made resource to reuse, and therefore need not service logic entity and specially resource is safeguarded; Thereby further reduced the expense of service logic entity, realized that big data quantity is mutual efficiently;
Once more; In the present embodiment; In the message header of the soap message that returns, carry Total and Current Sequence No, so the requesting party can determine whether to receive whole soap messages according to these information, when finding not receive whole soap messages; Can also be according to CurrentSequence No to the service end request repeat, thus reliability of data transmission improved.
Foregoing description service logic entity results set is carried out the data transmission procedure that subpackage is handled; It is understandable that; In practical application, can the service logic of service logic entity not adjusted, handle and accomplish subpackage by interceptor; See also Fig. 3, in the embodiment of the invention data transmission method again an embodiment comprise:
301～303, with embodiment shown in Figure 2 in step 201 to 203 identical, repeat no more here.
304, service logic entity is sent results set;
After service logic entity has got access to results set according to the Web service request message, can this results set be sent to Response Handler Chain.
In the present embodiment, service logic entity can be directly according to the mode of one-time request one response, no matter the data volume of results set has muchly, all in a soap message, issues Response HandlerChain.
305, interceptor is intercepted and captured results set, and judges whether to be one-time request multiple response pattern that if then execution in step 307, if not, then execution in step 306;
In the present embodiment; When service logic entity when Response Handler Chain sends results set; Interceptor can be intercepted and captured this results set; And the Web service request message of intercepting and capturing according to this results set and in step 301 judges whether to be one-time request multiple response pattern, and concrete deterministic process can be similar with the deterministic process of service logic entity among the embodiment shown in Figure 2, repeats no more here.
306, interceptor is carried out other handling processes;
If the Request Type in the message header information of Web service request message is not an indication one-time request multiple response pattern; Or the data volume of results set is less than or equal to the Max Number in the message header information of Web service request message; Then interceptor confirms it is not one-time request multiple response pattern; The soap message that comprises results set that this moment, interceptor can directly send service logic entity is forwarded to ResponseHandler Chain, and by Response Handler Chain this soap message is sent to the requesting party.
307, interceptor carries out subpackage according to the maximum amount of data parameter in the Web service request message to results set;
When interceptor is confirmed as one-time request multiple response pattern; Interceptor carries out subpackage according to the Max Number in the message header information of Web service request message to results set; The process of the process of concrete subpackage and middle service logic entity subpackage embodiment illustrated in fig. 2 is similar, repeats no more here.
308, interceptor sends through the passage object preceding N-1 data subpackage to the response process chain, and preceding N-1 data subpackage is sent to described request side through this response process chain;
After interceptor obtains N data subpackage; Can preceding N-1 data subpackage in this N the data subpackage be sent to Response Handler Chain through the passage object; Should preceding N-1 data subpackage be sent to the requesting party through Response Handler Chain; The process that concrete process of transmitting and middle service logic entity embodiment illustrated in fig. 2 are sent is similar, repeats no more here.
309, interceptor sends N data subpackage in this N the data subpackage to identical response process chain, and N data subpackage is sent to the requesting party through this response process chain.
When interceptor begins when Response Handler Chain sends N data subpackage, interceptor is at first removed the current relevant information of calling, the concrete information content and reset procedure and embodiment illustrated in fig. 2 in the process removed similar, repeat no more here.
It is thus clear that in the present embodiment, service logic entity is after getting access to results set; Interceptor can carry out subpackage to the result; And directly the data subpackage that obtains is sent to the requesting party, and promptly can realize returning and Flow Control of big data quantity, reach identical effect with the data transmission procedure of iterative manner of the prior art; And need not to wait for that the requesting party asks subsequent result once more in the present embodiment simultaneously; Therefore service logic entity need not to preserve the average information of transfer of data, thereby has reduced the expense of service logic entity, has realized that big data quantity is mutual efficiently;
Secondly; In the present embodiment; Because when interceptor sent last data subpackage, interceptor can be removed the current relevant information of calling automatically made resource to reuse, and therefore need not service logic entity and specially resource is safeguarded; Thereby further reduced the expense of service logic entity, realized that big data quantity is mutual efficiently;
Once more; In the present embodiment, service logic entity can be carried out business logic processing according to the mode of one-time request one response fully, handles and carry out subpackage by interceptor; Therefore can further reduce the expense of service logic entity, realize that big data quantity is mutual efficiently.
Introduce the data transmission system in the embodiment of the invention below, see also Fig. 4, data transmission system one embodiment comprises in the embodiment of the invention:
Need to prove that interceptor 401 specifically can be judged last data subpackage that this data subpackage is a results set according to the message header of this N data subpackage, should be understood that, also can judge; The said current relevant information of calling can further include the passage object and quotes etc. JAXWS operation is contextual.
For ease of understanding, with a concrete application scenarios data transmission system in the present embodiment is described below:
In the present embodiment, when the requesting party sent the Web service request message to service end, this Web service request message can pass through the communication aspect, got into the Request Handler Chain of JAXWS definition.
Pass through Request Handler Chain in the process that the service logic entity 402 of service end is sent at this Web service request message; Can be intercepted and captured by interceptor 401; Interceptor 401 can extract the current JAXWS operation context that calls; Concrete JAXWS moves context and extracts the current JAXWS that calls and move the common practise that contextual process is those skilled in the art, does not limit here.
After service logic entity 402 is getting access to results set; Can judge whether to be one-time request multiple response pattern according to the message header information of this results set and Web service request message; The deterministic process of describing among concrete deterministic process and the aforementioned embodiment shown in Figure 2 is identical, repeats no more here.
When service logic entity 402 is confirmed as one-time request multiple response pattern; Service logic entity 402 is carried out subpackage according to the Max Number in the message header information of Web service request message to results set; The process of concrete subpackage can adopt average subpackage; Or subpackage at random, or other branch packet procedures, as long as make the data volume of each data subpackage all be less than or equal to Max Number.
After 402 pairs of results sets of service logic entity are accomplished subpackage, obtain N data subpackage, service logic entity 402 all is encapsulated as an independently soap message with each data subpackage again, promptly obtains N soap message.
After service logic entity 402 obtains N soap message; Service logic entity 402 can extract the passage object from the local storage of current thread; Send preceding N-1 soap message in N the soap message to this passage object; The passage object extracts JAXWS operation context more afterwards; And move from this JAXWS and to obtain quoting of Response Handler Chain the contextual internal damping, preceding N-1 soap message in N the soap message is sent to this Response Handler Chain, and N-1 soap message is sent to the requesting party by this Response Handler Chain.
After service logic entity has been sent a preceding N-1 soap message; Last (promptly N) soap message adopts normal echo plex mode to return; Promptly directly this N soap message sent to Response Handler Chain, be back to the requesting party by Response Handler Chain.
Need to prove; In the present embodiment, this N soap message can be intercepted and captured by interceptor 401 before arriving Response HandlerChain, and this moment, interceptor 401 confirmed that according to the message header of this N soap message this soap message is last data subpackage of results set; Then interceptor 401 is carried out relevant cleaning work; Remove the current relevant information of calling, wherein comprise the passage object at least, can further include the passage object and quote etc. JAXWS operation is contextual.
Need to prove; Interceptor 401 in the present embodiment can not judged the soap message that receives equally; Owing to have only N soap message just can pass through interceptor, therefore, interceptor can be set in the present embodiment in a single day receive soap message and promptly carry out relevant cleaning work.
It is thus clear that in the present embodiment, service logic entity 402 is after getting access to results set; Can carry out subpackage to the result; And directly the data subpackage that obtains is sent to the requesting party, and promptly can realize returning and Flow Control of big data quantity, reach identical effect with the data transmission procedure of iterative manner of the prior art; And need not to wait for that the requesting party asks subsequent result once more in the present embodiment simultaneously; Therefore service logic entity 402 need not to preserve the average information of transfer of data, thereby has reduced the expense of service logic entity 402, has realized that big data quantity is mutual efficiently;
Secondly; In the present embodiment; Because when service logic entity 402 was sent last data subpackage, interceptor 401 can be removed the current relevant information of calling automatically made resource to reuse, and therefore need not service logic entity 402 and specially resource is safeguarded; Thereby further reduced the expense of service logic entity, realized that big data quantity is mutual efficiently.
Introduce the another kind of data transmission system in the embodiment of the invention below, see also Fig. 4 equally, another embodiment of data transmission system comprises in the embodiment of the invention:
For ease of understanding, with a concrete application scenarios data transmission system in the present embodiment is described below:
In the present embodiment, when the requesting party sent the Web service request message to service end, this Web service request message can pass through the communication aspect, got into the Request Handler Chain of JAXWS definition.
Pass through Request Handler Chain in the process that the service logic entity 402 of service end is sent at this Web service request message; Can be intercepted and captured by interceptor 401; Interceptor 401 can extract the current JAXWS operation context that calls; Concrete JAXWS moves context and extracts the current JAXWS that calls and move the common practise that contextual process is those skilled in the art, does not limit here.
After service logic entity 402 has got access to results set according to the Web service request message, can this results set be sent to Response Handler Chain.
In the present embodiment, service logic entity 402 can be directly according to the mode of one-time request one response, no matter the data volume of results set has muchly, all in a soap message, issues Response HandlerChain.
When service logic entity 402 when Response Handler Chain sends results set; Interceptor 401 can be intercepted and captured this results set; And judge whether to be one-time request multiple response pattern according to the Web service request message of this results set and intercepting and capturing; Concrete deterministic process can be similar with the deterministic process among the embodiment shown in Figure 3, repeats no more here.
When interceptor 401 is confirmed as one-time request multiple response pattern; Interceptor 401 carries out subpackage according to the Max Number in the message header information of Web service request message to results set; The process of the process of concrete subpackage and middle subpackage embodiment illustrated in fig. 3 is similar, repeats no more here.
After interceptor 401 obtains N data subpackage; Can preceding N-1 data subpackage in this N the data subpackage be sent to Response Handler Chain through the passage object; Concrete process of transmitting and middle process of sending embodiment illustrated in fig. 3 are similar, repeat no more here.
When interceptor 401 begins when Response Handler Chain sends N data subpackage; Interceptor is at first removed the current relevant information of calling; The concrete information content and reset procedure and the middle process of removing embodiment illustrated in fig. 3 are similar, repeat no more here.
It is thus clear that in the present embodiment, service logic entity 402 is after getting access to results set; Interceptor 401 can carry out subpackage to the result; And directly the data subpackage that obtains is sent to the requesting party, and promptly can realize returning and Flow Control of big data quantity, reach identical effect with the data transmission procedure of iterative manner of the prior art; And need not to wait for that the requesting party asks subsequent result once more in the present embodiment simultaneously; Therefore service logic entity 402 need not to preserve the average information of transfer of data, thereby has reduced the expense of service logic entity 402, has realized that big data quantity is mutual efficiently;
Secondly; In the present embodiment; Because when interceptor 401 sent last data subpackage, interceptor 401 can be removed the current relevant information of calling automatically made resource to reuse, and therefore need not service logic entity 402 and specially resource is safeguarded; Thereby further reduced the expense of service logic entity 402, realized that big data quantity is mutual efficiently;
Once more; In the present embodiment, service logic entity 402 can be carried out business logic processing according to the mode of one-time request one response fully, handles and carry out subpackage by interceptor 401; Therefore can further reduce the expense of service logic entity, realize that big data quantity is mutual efficiently.
Need to prove that the data transmission system of describing in the foregoing description can be deployed in the unit, also can the different units in the data transmission system be deployed in the different equipment that concrete deployment way does not limit here.
Introduce a kind of service logic entity embodiment in the embodiment of the invention below, see also Fig. 5, the service logic entity in the embodiment of the invention comprises:
Acquiring unit 501 is used to obtain the network Web service request message that the requesting party sends;
In the present embodiment; Acquiring unit 501 can obtain the Web service request message from interceptor; Also can obtain the Web service request message from the requesting party, the acquisition process of describing among concrete acquisition process and earlier figures 1 and the embodiment shown in Figure 2 is identical, repeats no more here.
Business logic processing unit 502 is used for obtaining results set according to the Web service request message;
The first subpackage unit 503 when being used to confirm as one-time request multiple response pattern (specifically can be to confirm as one-time request multiple response pattern according to Web service request message and results set), carrying out the subpackage processing to results set and obtains N data subpackage;
Under a kind of realization, the first subpackage unit 503 in the present embodiment comprises:
First judging unit 5031 is used to judge whether be one-time request multiple response pattern (specifically can be to confirm as one-time request multiple response pattern according to Web service request message and results set);
For ease of understanding, with a concrete application scenarios service logic entity embodiment in the present embodiment is described below:
In the present embodiment, when the requesting party sent the Web service request message to service end, this Web service request message can pass through the communication aspect, got into the Request Handler Chain of JAXWS definition.
Acquiring unit 501 can directly receive the Web service request message from the requesting party; Perhaps get access to the Web service request message that the requesting party sends from interceptor; Before this; Interceptor can at first be intercepted and captured the Web service request message that the requesting party sends and create the passage object, and concrete constructive process is identical with establishment mode among the aforementioned embodiment shown in Figure 2.
After interceptor has been created the passage object; Business logic processing unit 502 can obtain corresponding results set according to the Web service request message that gets access to; Be the content of requestor requests, concrete acquisition process is those skilled in the art's a common practise, does not limit here.
After business logic processing unit 502 gets access to results set; Then first judging unit 5031 can judge whether to be one-time request response modes repeatedly according to Web service request message and this results set; If; Then first performance element 5032 can carry out subpackage to this results set according to the parameter in the Web service request message and handles and to obtain N data subpackage, and first encapsulation unit 5033 all is encapsulated as independently soap message with each the data subpackage in N the data subpackage afterwards.
After having accomplished the branch package operation; Obtain N data subpackage; First transmission unit 504 is sent to the passage object with preceding N-1 data subpackage wherein; By this passage object this N-1 data subpackage is sent to the response process chain again, finally this N-1 data subpackage is sent to the requesting party by this response process chain.
After first transmission unit 504 has been accomplished the transmission of preceding N-1 data subpackage; First transmission unit 504 is with last data subpackage; I.e. N data subpackage sent according to normal echo plex mode, promptly not through the passage object; But directly send this N data subpackage to the response process chain, finally this N data subpackage is sent to the requesting party by this response process chain.
It is thus clear that in the embodiment of the invention, the first subpackage unit 503 is after getting access to results set; Can carry out subpackage to results set; First transmission unit 504 directly is sent to the requesting party with the data subpackage that obtains, and need not to wait for that the requesting party asks subsequent result once more, so service logic entity need not to preserve the average information of transfer of data; Thereby reduced the expense of service logic entity, realized the ability of big data quantity exchange efficiently.
Introduce a kind of interceptor embodiment in the embodiment of the invention below, see also Fig. 6, the interceptor embodiment in the embodiment of the invention comprises:
Intercept and capture unit 601, be used to intercept and capture the network Web service request message of requesting party's transmission and intercept and capture the results set that service logic entity is returned;
Create unit 602, be used to create the passage object;
The second subpackage unit 603 is used for when confirming as one-time request multiple response pattern (specifically can be to confirm as one-time request multiple response pattern according to Web service request message and results set), results set is carried out the subpackage processing obtain N data subpackage;
Under a kind of realization, the second subpackage unit 603 in the present embodiment can comprise:
Under a kind of realization, the interceptor in the present embodiment can further include:
Remove unit 605, be used for removing the current relevant information of calling in that preceding N-1 data subpackage of N data subpackage passed through the passage object after Response Handler Chain sends, current calling comprises the passage object at least in the relevant information.
For ease of understanding, with a concrete application scenarios interceptor embodiment in the present embodiment is described below:
In the present embodiment, when the requesting party sent the Web service request message to service end, this Web service request message can pass through the communication aspect, got into the Request Handler Chain of JAXWS definition.
Pass through Request Handler Chain in the process that the service logic entity of service end is sent at this Web service request message; Can be intercepted and captured unit 601 intercepts and captures; Create unit 602 and can extract the current JAXWS operation context that calls; Create with current and call corresponding passage object, and the JAXWS that gets access to is moved context be stored in the passage object, and with the passage object storage in the current thread local that calls is stored.
When service logic entity when Response Handler Chain sends results set; Intercept and capture unit 601 and can intercept and capture this results set; Second judging unit 6031 judges whether to be one-time request multiple response pattern according to this results set and at the Web service request message of intercepting and capturing before; Concrete deterministic process can be similar with the deterministic process among the embodiment shown in Figure 3, repeats no more here.
When second judging unit 6031 is confirmed as one-time request multiple response pattern; Second performance element 6032 carries out subpackage according to the Max Number in the message header information of Web service request message to results set; And each the data subpackage in N the data subpackage all is encapsulated as independently soap message by second encapsulation unit 6033; The process of the process of concrete subpackage and middle subpackage embodiment illustrated in fig. 3 is similar, repeats no more here.
After obtaining N data subpackage; Second transmission unit 604 can send through the passage object preceding N-1 data subpackage in this N the data subpackage to Response Handler Chain; Preceding N-1 data subpackage is sent to the requesting party through Response Handler Chain; Concrete process of transmitting and middle process of sending embodiment illustrated in fig. 3 are similar, repeat no more here.
When second transmission unit 604 begins when Response Handler Chain sends N data subpackage; Remove unit 605 and at first remove the current relevant information of calling; The concrete information content and reset procedure and the middle process of removing embodiment illustrated in fig. 3 are similar, repeat no more here.
Thus it is clear that, in the present embodiment, intercept and capture unit 601 after getting access to results set; The second subpackage unit 603 can carry out subpackage to the result; And directly the data subpackage that obtains is sent to the requesting party, and promptly can realize returning and Flow Control of big data quantity, reach identical effect with the data transmission procedure of iterative manner of the prior art; And need not to wait for that the requesting party asks subsequent result once more in the present embodiment simultaneously; Therefore service logic entity need not to preserve the average information of transfer of data, thereby has reduced the expense of service logic entity 402, has realized that big data quantity is mutual efficiently;
Secondly; In the present embodiment; Because when second transmission unit 604 sent last data subpackage, the current relevant information of calling can be removed automatically in removing unit 605 made resource to reuse, and therefore need not service logic entity and specially resource is safeguarded; Thereby further reduced the expense of service logic entity, realized that big data quantity is mutual efficiently;
Once more; In the present embodiment, service logic entity can be carried out business logic processing according to the mode of one-time request one response fully, handles and carry out subpackage by the second subpackage unit 603; Therefore can further reduce the expense of service logic entity, realize that big data quantity is mutual efficiently.
One of ordinary skill in the art will appreciate that all or part of step that realizes in the foregoing description method is to instruct relevant hardware to accomplish through program; Described program can be stored in a kind of computer-readable recording medium; The above-mentioned storage medium of mentioning can be a read-only memory, disk or CD etc.
More than a kind of data transmission method provided by the present invention and data transmission system and relevant device have been carried out detailed introduction; For one of ordinary skill in the art; Thought according to the embodiment of the invention; The part that on embodiment and range of application, all can change, in sum, this description should not be construed as limitation of the present invention.
Claims (19)
1. a data transmission method is applied to the network Web service, it is characterized in that, comprising:
After interceptor was intercepted and captured the Web service request message of requesting party's transmission and created the passage object, service logic entity obtained results set according to said Web service request message;
When confirming as one-time request multiple response pattern, said results set is carried out the subpackage processing obtain N data subpackage;
Preceding N-1 data subpackage in said N the data subpackage sent to response process chain Response Handler Chain through said passage object, and said preceding N-1 data subpackage is sent to described request side through said Response Handler Chain;
N data subpackage in said N the data subpackage sent to said Response Handler Chain according to normal echo plex mode, and said N data subpackage is sent to described request side through said Response Handler Chain;
Said establishment passage object comprises:
Interceptor is created with current and is called corresponding passage object after intercepting and capturing the Web service request message that the requesting party sends;
Extract the current network Web service application programming interfaces operation context that calls;
Said context is stored in the said passage object, and in the thread local storage that said passage object storage is called in current.
2. data transmission method according to claim 1 is characterized in that, when interceptor is passed through in said N data subpackage, makes said interceptor remove the current relevant information of calling, and said current calling comprises said passage object at least in the relevant information.
3. data transmission method according to claim 1 is characterized in that, saidly results set is carried out subpackage handles and to obtain N data subpackage and comprise:
According to the maximum amount of data parameter in the said Web service request message said results set is carried out the subpackage processing and obtain N data subpackage;
Each data subpackage in said N the data subpackage all is encapsulated as the Simple Object Access Protocol soap message.
4. data transmission method according to claim 1 is characterized in that, the said one-time request multiple response pattern of confirming as comprises:
Request type parametric representation in said Web service request message is an one-time request multiple response pattern, and the data volume of said results set is confirmed as one-time request multiple response pattern during greater than the maximum amount of data parameter in the said Web service request message.
5. according to each described data transmission method in the claim 1 to 4; It is characterized in that; Said preceding N-1 data subpackage in N the data subpackage sent to Response Handler Chain through said passage object, said before N-1 data subpackage pass through said Response Handler Chain and be sent to described request side and comprise:
From current thread local storage of calling, extract said passage object;
N-1 data subpackage before said is sent to said passage object, and the association identification in the message header of said preceding N-1 data subpackage is corresponding with the association identification in the message header of said Web service request message;
By said passage object N-1 data subpackage before said is sent to the Response Handler Chain in the internal damping, said preceding N-1 data subpackage is sent to the requesting party through said Response Handler Chain.
6. data transmission method according to claim 2; It is characterized in that; Said N data subpackage in N the data subpackage sent to said Response Handler Chain, said N data subpackage is sent to described request side through said Response Handler Chain and comprises:
Send said N data subpackage to said Response Handler Chain, make that interceptor is intercepted and captured said N data subpackage after, remove the current relevant information of calling, said current calling comprises said passage object at least in the relevant information;
By said interceptor said N data subpackage is sent to said Response Handler Chain, said N data subpackage is sent to the requesting party via said Response Handler Chain.
7. data transmission method according to claim 1 is characterized in that, comprises request type in the header of first data subpackage in said N data subpackage; Association identification; Sum and current sequence number, wherein: the described request type is designated as one-time request multiple response mode, and said association identification is corresponding with the association identification in the said Web service request message; The number of said total designation data subpackage, the sequence number of the data subpackage that said current sequence number indication is current;
Second comprises request type in said N the data subpackage to the header of N-1 data subpackage; Association identification and current sequence number; Wherein: the described request type is designated as one-time request multiple response mode; Said association identification is corresponding with the association identification in the said Web service request message, the sequence number of the data subpackage that said current sequence number indication is current;
Comprise request type in the header of N data subpackage in said N data subpackage; Association identification; Current sequence number and end sign, wherein: the described request type is designated as one-time request multiple response mode, and said association identification is corresponding with the association identification in the said Web service request message; The sequence number of the data subpackage that said current sequence number indication is current, the subpackage of said end sign designation data is sent and is finished.
8. a data transmission method is characterized in that, comprising:
Intercept and capture the network Web service request message of requesting party's transmission and create the passage object;
Intercept and capture the results set that service logic entity is returned, said results set is obtained according to said Web service request message by service logic entity;
When confirming as one-time request multiple response pattern, results set is carried out the subpackage processing obtain N data subpackage;
Preceding N-1 data subpackage in said N the data subpackage sent to response process chain Response Handler Chain through said passage object, and said preceding N-1 data subpackage is sent to described request side through said Response Handler Chain;
N data subpackage in said N the data subpackage sent to said Response Handler Chain according to normal echo plex mode, and said N data subpackage is sent to described request side through said Response Handler Chain;
Said establishment passage object comprises:
Interceptor is created with current and is called corresponding passage object after intercepting and capturing the Web service request message that the requesting party sends;
Extract the current network Web service application programming interfaces operation context that calls;
Said context is stored in the said passage object, and in the thread local storage that said passage object storage is called in current.
9. data transmission method according to claim 8 is characterized in that, preceding N-1 data subpackage in said N the data subpackage comprised after response process chain Response Handler Chain sends through said passage object:
Remove the current relevant information of calling, said current calling comprises said passage object at least in the relevant information.
10. according to Claim 8 or 9 described data transmission methods, it is characterized in that, saidly results set is carried out subpackage handle and obtain N data subpackage and comprise:
According to the maximum amount of data parameter in the said Web service request message said results set is carried out the subpackage processing and obtain N data subpackage;
Each data subpackage in said N the data subpackage all is encapsulated as the Simple Object Access Protocol soap message.
11. a data transmission system is characterized in that, comprising:
Interceptor is used to intercept and capture the network Web service request message that the requesting party sends, and creates the passage object;
Service logic entity; Be used for obtaining results set according to the Web service request message that receives; When confirming as one-time request multiple response pattern; Said results set is carried out the subpackage processing obtain N data subpackage, preceding N-1 data subpackage in said N the data subpackage sent to response process chain Response Handler Chain through said passage object, said preceding N-1 data subpackage is sent to described request side through said Response Handler Chain; N data subpackage in said N the data subpackage sent to said Response Handler Chain according to normal echo plex mode, and said N data subpackage is sent to described request side through said Response Handler Chain;
Said interceptor is created the passage object and is specially: interceptor is created with current and is called corresponding passage object after intercepting and capturing the Web service request message that the requesting party sends; Extract the current network Web service application programming interfaces operation context that calls; Said context is stored in the said passage object, and in the thread local storage that said passage object storage is called in current.
12. data transmission system according to claim 11; It is characterized in that; Said interceptor also is used to intercept and capture said N data subpackage, and after intercepting and capturing, removes the current relevant information of calling; Said current calling comprises said passage object at least in the relevant information, said N data subpackage is sent to said Response Handler Chain.
13. a data transmission system is characterized in that, comprising:
Interceptor; Be used to intercept and capture the Web service request message that the requesting party sends; Create the passage object; Intercept and capture the results set that service logic entity is sent, when confirming as one-time request multiple response pattern, said results set is carried out subpackage obtain N data subpackage; Preceding N-1 data subpackage in said N the data subpackage sent to response process chain Response Handler Chain through said passage object, and said preceding N-1 data subpackage is sent to described request side through said Response Handler Chain; N data subpackage in said N the data subpackage sent to said Response Handler Chain according to normal echo plex mode, and said N data subpackage is sent to described request side through said Response Handler Chain;
Service logic entity is used for obtaining the corresponding results set according to the Web service request message that receives, and returns said results set;
Said interceptor is created the passage object and is specially: interceptor is created with current and is called corresponding passage object after intercepting and capturing the Web service request message that the requesting party sends; Extract the current network Web service application programming interfaces operation context that calls; Said context is stored in the said passage object, and in the thread local storage that said passage object storage is called in current.
14. data transmission system according to claim 13; It is characterized in that; Said interceptor also is used for preceding N-1 data subpackage of said N data subpackage removed the current relevant information of calling through said passage object after Response Handler Chain sends, and said current calling comprises said passage object at least in the relevant information.
15. a service logic entity is characterized in that, comprising:
Acquiring unit is used to obtain the network Web service request message that the requesting party sends;
The business logic processing unit is used for obtaining results set according to said Web service request message;
The first subpackage unit when being used to confirm as one-time request multiple response pattern, carrying out the subpackage processing to said results set and obtains N data subpackage;
First transmission unit; Be used for preceding N-1 data subpackage of said N data subpackage sent to response process chain Response Handler Chain through the passage object, said preceding N-1 data subpackage is sent to described request side through said Response Handler Chain; N data subpackage in said N the data subpackage sent to said Response Handler Chain according to normal echo plex mode, and said N data subpackage is sent to described request side through said Response Handler Chain.
16. service logic entity according to claim 15 is characterized in that, the said first subpackage unit comprises:
First judging unit is used for judging whether to be one-time request multiple response pattern according to said Web service request message and said results set;
First performance element is used for when confirming as one-time request multiple response pattern, according to the maximum amount of data parameter in the said Web service request message said results set is carried out the subpackage processing and obtains N data subpackage;
First encapsulation unit is used for each data subpackage of said N data subpackage all is encapsulated as independently Simple Object Access Protocol soap message.
17. an interceptor is characterized in that, comprising:
Intercept and capture the unit, be used to intercept and capture the network Web service request message of requesting party's transmission and intercept and capture the results set that service logic entity is returned;
Create the unit, be used to create the passage object;
The second subpackage unit is used for when confirming as one-time request multiple response pattern, results set is carried out the subpackage processing obtain N data subpackage;
Second transmission unit; Be used for preceding N-1 data subpackage of said N data subpackage sent to response process chain Response Handler Chain through said passage object, said preceding N-1 data subpackage is sent to described request side through said Response Handler Chain; N data subpackage in said N the data subpackage sent to said Response Handler Chain according to normal echo plex mode, and said N data subpackage is sent to described request side through said Response Handler Chain;
Said establishment unit is created the passage object and is specially: after intercepting and capturing the Web service request message that the requesting party sends, create with current and call corresponding passage object; Extract the current network Web service application programming interfaces operation context that calls; Said context is stored in the said passage object, and in the thread local storage that said passage object storage is called in current.
18. interceptor according to claim 17 is characterized in that, the said second subpackage unit comprises:
Second judging unit is used for judging whether to be one-time request multiple response pattern according to said Web service request message and said results set;
Second performance element is used for when confirming as one-time request multiple response pattern, according to the maximum amount of data parameter in the said Web service request message said results set is carried out the subpackage processing and obtains N data subpackage;
Second encapsulation unit is used for each data subpackage of said N data subpackage all is encapsulated as independently Simple Object Access Protocol soap message.
19., it is characterized in that said interceptor also comprises according to claim 17 or 18 described interceptors:
Remove the unit; Be used for preceding N-1 data subpackage of said N data subpackage passed through said passage object after Response Handler Chain sends; Remove the current relevant information of calling, said current calling comprises said passage object at least in the relevant information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910167149A CN101635744B (en) | 2009-08-26 | 2009-08-26 | Method and system for transmitting data and relative equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910167149A CN101635744B (en) | 2009-08-26 | 2009-08-26 | Method and system for transmitting data and relative equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101635744A CN101635744A (en) | 2010-01-27 |
| CN101635744B true CN101635744B (en) | 2012-08-29 |
Family
ID=41594802
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910167149A Expired - Fee Related CN101635744B (en) | 2009-08-26 | 2009-08-26 | Method and system for transmitting data and relative equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101635744B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108628683A (en) * | 2017-03-20 | 2018-10-09 | 腾讯科技（深圳）有限公司 | Data transmission method and device |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101860549B (en) * | 2010-06-25 | 2013-03-27 | 山东中创软件商用中间件股份有限公司 | Access session data processing method under Web Service and device |
| CN102130954A (en) * | 2011-03-17 | 2011-07-20 | 华为技术有限公司 | Method and device for transmitting data resources |
| CN102917021A (en) * | 2012-09-19 | 2013-02-06 | 深圳市融创天下科技股份有限公司 | Method, system and terminal equipment for returning data on basis of Web service |
| CN102891768A (en) * | 2012-10-11 | 2013-01-23 | 华为技术有限公司 | Method and network element for network management |
| CN108733598B (en) * | 2018-05-07 | 2021-05-18 | 浪潮集团有限公司 | Data transmission method and data transmission device |
| CN110058940B (en) * | 2019-03-08 | 2022-11-22 | 苏宁易购集团股份有限公司 | Data processing method and device in multi-thread environment |
| CN110446228B (en) * | 2019-08-13 | 2022-02-22 | 腾讯科技（深圳）有限公司 | Data transmission method, device, terminal equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1615618A (en) * | 2002-08-14 | 2005-05-11 | Lg电子株式会社 | A bi-directional packet data transmission system and method |
| CN1642317A (en) * | 2004-01-13 | 2005-07-20 | 英华达（南京）科技有限公司 | Method for low-power hand set down-loading document data through personal computer |
| CN1992603A (en) * | 2005-12-30 | 2007-07-04 | 萧学文 | Method and system for implementing data-transmission under wireless network environment |
-
2009
- 2009-08-26 CN CN200910167149A patent/CN101635744B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1615618A (en) * | 2002-08-14 | 2005-05-11 | Lg电子株式会社 | A bi-directional packet data transmission system and method |
| CN1642317A (en) * | 2004-01-13 | 2005-07-20 | 英华达（南京）科技有限公司 | Method for low-power hand set down-loading document data through personal computer |
| CN1992603A (en) * | 2005-12-30 | 2007-07-04 | 萧学文 | Method and system for implementing data-transmission under wireless network environment |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108628683A (en) * | 2017-03-20 | 2018-10-09 | 腾讯科技（深圳）有限公司 | Data transmission method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101635744A (en) | 2010-01-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101635744B (en) | Method and system for transmitting data and relative equipment | |
| CN102301784B (en) | Method and system for computing and sending resource requests and avoiding deadlock situations in mobile communication system | |
| FR3042087A1 (en) | METHOD FOR TRANSMITTING SWITCHED DATA PACKETS BETWEEN A CONTENTION CHANNEL (RACH) AND A RESERVE CHANNEL ON DEMAND (DAMA) | |
| CN107360247B (en) | The method and the network equipment of processing business | |
| GB2493129A (en) | Managing a SIP server | |
| MX2007011787A (en) | System and method for simultaneous voice and data call over wireless infrastructure. | |
| CN110958281A (en) | Data transmission method and communication device based on Internet of things | |
| EP3155788B1 (en) | Proxy node for transferring packets between a server and a client using port sharding | |
| CN112491944A (en) | Edge application discovery method and device, and edge application service support method and device | |
| CN105635083A (en) | Service processing method and service processing system based on server and client architecture | |
| JP2019525578A (en) | Efficient forwarding of encapsulated media traffic through a datagram-based transport layer | |
| GB2493130A (en) | SIP server overload control | |
| KR20150100926A (en) | Offload method, device and system | |
| CN110022332B (en) | Hypertext transfer security protocol proxy method, device, equipment and medium | |
| CN110582090A (en) | CDN scheduling method, scheduling system and MEC network element | |
| CN109120578B (en) | Method and device for realizing link connection processing | |
| CN112291180A (en) | Message load balancing method | |
| CN103475506B (en) | Multiple equipment management control method and system | |
| CN109525539B (en) | Capability calling method, call receipt method, information processing method and system | |
| CN114666846A (en) | Communication method and gateway equipment | |
| CN105230074B (en) | Video cache switching handling method, device and system | |
| CN110166185B (en) | Audio data processing method and device, storage medium and processor | |
| EP3107352B1 (en) | Information transfer method, system and apparatus | |
| CN112165529A (en) | Method, device, equipment and medium for low-cost cross-network data exchange | |
| EP2124413B1 (en) | System and method for carrying out communication between a server and a user equipment |
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 | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20120829 Termination date: 20130826 |