CN1842071B - Realization method and apparatus for application program access Web server end object - Google Patents
Realization method and apparatus for application program access Web server end object Download PDFInfo
- Publication number
- CN1842071B CN1842071B CN2005100593169A CN200510059316A CN1842071B CN 1842071 B CN1842071 B CN 1842071B CN 2005100593169 A CN2005100593169 A CN 2005100593169A CN 200510059316 A CN200510059316 A CN 200510059316A CN 1842071 B CN1842071 B CN 1842071B
- Authority
- CN
- China
- Prior art keywords
- stake
- pond
- publicly
- private
- module
- 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
- Stored Programmes (AREA)
Abstract
The invention discloses a method for achieving the applied program to visit the Web server end object. The method arranges a light weight stage accommodator between the small applied program and Web server; the light weight stage accommodator is divided into client end post and server end post; when the small applied program sends the calling pleasing to the Web server, the client end post holds up all of the pleasing and sends it to the server end post which transmits the pleasing to the Web server; it uses the controller to control the calling of the pleasing.
Description
Technical field
The present invention relates to areas of information technology, relate to a kind of implementation method and device of application program access Web server end object or rather.
Background technology
In the design of the web of sandwich construction web applications, use a kind of applet (Applet) that runs under the browser to represent a layer technology usually as the client of complexity.
Existing Applet called Web service end resource, the scheme of main usefulness is to adopt RMI RMI (Remote Method Invocation) mode, and as shown in Figure 1, Applet at first calls the RMI service, carry out the serializing of Web server object by RMI, pass to Applet again.
This technical scheme has following shortcoming:
1, need set up the RMI service at server end, increase the pressure of server;
2, need to have limited its use under complex network structures specially for RMI offers corresponding ports;
3, have under the environment of fire compartment wall, need open corresponding ports specially, reduce the fail safe of whole system;
4, not to the object cache management of classifying, only be the framework of a far call, under the concurrent condition of height, can cause the performance of server end sharply to descend.
The scheme of existing another kind of Applet called Web service end resource as shown in Figure 2, Applet directly communicates by letter by overlapping joint word Socket with the operation servlet Servlet thereon of web server end, the request format, service end is by monitoring, resolve concrete request, call suitable object again.Applet at first needs different requests is encoded, and request call is passed to the Servlet of service end, resolves original request coding by Servlet is anti-, calls corresponding object more as required.
This technical scheme has following shortcoming:
1, need encode to calling, make mistakes easily, should not debug;
2, can't satisfy the object that calls complexity, workload is big;
3, not to the remote object cache management of classifying, under the concurrent condition of height, can cause the performance of service end sharply to descend.
Existing Applet calls the technology of service end or the framework that provides is too thick and heavy, or is not suitable for complicated network configuration.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of implementation method and device of application program access Web server end object, does not need to offer special monitoring service, solves complexity and difficult debugging problem that simple Applet directly calls.
For reaching above purpose, the invention provides following technical scheme:
A kind of implementation method of application program access Web server end object wherein, is provided with a lightweight adapter between Applet end and Web server, the lightweight adapter is divided into client stake and service end stake, and described method comprises the steps:
A, Applet initiate call request to the Web server end;
B, client stake are tackled described Applet and to the request of server and by built-in tunnel the service end stake are submitted in request;
C, service end stake are passed to Web server with described request, by controller according to request, whether the object of determining call request leaves in the private object pond that sets in advance, if, then from the private object pond, obtain object and make it be back to applet via service end stake and client stake;
If not in the private object pond, search in the publicly-owned object pool that sets in advance and whether deposited available objects, if have, then make this object be back to applet by service end stake and client stake, if do not have, directly the scheduling Web server obtains available objects, and makes this object be back to applet through service end stake and client stake.
Step B comprises that further the client stake encodes to request, and the service end stake is submitted in the request behind the coding; Step C further comprises after the service end stake is decoded to described request described request is passed to Web server.
In step C, after obtaining available objects from publicly-owned object pool, directly this available objects is back to applet via service end stake and client stake by publicly-owned object pool, perhaps, earlier this object is moved on in the private object pond, obtain object and be back to applet through service end stake and client stake by the private object pond;
Perhaps, in step C, after obtaining available objects from Web server, to be put in the publicly-owned object pool after this object initialization, directly available objects is back to applet through service end stake and client stake successively by publicly-owned object pool, or directly described available objects is positioned over the private object pond, will obtain object by the private object pond again and be back to applet through service end stake and client stake successively, or directly object will be back to applet through service end stake and client stake successively.
A kind of intelligent scheduler comprises that client-requested receiver module, object search module, publicly-owned object pool administration module and private object pond administration module, wherein,
The client-requested receiver module is used for linking to each other with the service end stake, receiving the call request that applet is initiated, and described request is forwarded to object searches module;
Described object is searched module and is used for linking to each other with WEB server, publicly-owned object pool and private object pond, receive the request that the client-requested receiver module is transmitted, search private object pond, publicly-owned object pool or WEB server according to request, lookup result is forwarded to publicly-owned object pool administration module or private object pond administration module;
It is mutual that private object pond administration module is searched module with object, accepts operation and management that lookup result carries out the private object pond;
It is mutual that publicly-owned object pool administration module is searched module with object, accepts operation and management that lookup result carries out publicly-owned object pool;
Whether the object that described intelligent scheduler is judged described call request in the private object pond, if in the private object pond, then obtains described object, and makes described object be back to applet via service end stake and client stake successively from the private object pond;
If not in the private object pond, then search described object whether in publicly-owned object pool, if in publicly-owned object pool, then described object is back to applet via service end stake and client stake by publicly-owned object pool, perhaps earlier described object is moved on in the private object pond, obtain object and be back to applet through service end stake and client stake by the private object pond; If not in publicly-owned object pool, then obtain described object from the WEB server, will be put in the publicly-owned object pool after the described object initialization, by publicly-owned object pool described object is back to applet through service end stake and client stake successively; Or described object is positioned over the private object pond, by the private object pond described object is back to applet through service end stake and client stake successively again; Perhaps described object is back to applet through service end stake and client stake successively.
A kind of intelligent scheduler comprises that client-requested receiver module, object search module, request processing module, publicly-owned object pool administration module, private object pond administration module and scheduling strategy module, wherein,
The client-requested receiver module is used for linking to each other with the service end stake, receiving the call request that applet is initiated, and described request is forwarded to the scheduling strategy module;
Described object is searched module and is used for linking to each other with WEB server, publicly-owned object pool and private object pond, the query statement that the receiving scheduling policy module issues, search private object pond, publicly-owned object pool or WEB server according to instruction, lookup result is forwarded to scheduling strategy module, publicly-owned object pool administration module or private object pond administration module;
The scheduling strategy module is used for searching module, client-requested receiver module, publicly-owned object pool administration module, private object pond administration module, request processing module with object and links to each other, receive the call request that connection module sends according to client-requested, determine this processing of request mode, issue processing instruction to object according to described processing mode and search module or request processing module, and accepting object searches the process information that module or request processing module are returned, and the scheduling strategy instruction is sent to private object pond administration module or publicly-owned object pool administration module;
Request processing module links to each other with the scheduling policy module, accepts the processing instruction that the scheduling strategy module issues described request is handled;
Private object pond administration module searches module with object and the scheduling strategy module is mutual, accepts the instruction carrying out of lookup result and the scheduling strategy operation and the management in private object pond;
Publicly-owned object pool administration module searches module with object and the scheduling strategy module is mutual, accepts the instruction carrying out of lookup result and the scheduling strategy operation and the management of publicly-owned object pool;
Whether the object that described intelligent scheduler is judged described call request in the private object pond, if in the private object pond, then obtains described object, and makes described object be back to applet via service end stake and client stake successively from the private object pond;
If not in the private object pond, then search described object whether in publicly-owned object pool, if in publicly-owned object pool, then described object is back to applet via service end stake and client stake by publicly-owned object pool, perhaps earlier described object is moved on in the private object pond, obtain object and be back to applet through service end stake and client stake by the private object pond;
If not in publicly-owned object pool, then obtain described object from the WEB server, will be put in the publicly-owned object pool after the described object initialization, by publicly-owned object pool described object is back to applet through service end stake and client stake successively; Or described object is positioned over the private object pond, by the private object pond described object is back to applet through service end stake and client stake successively again; Perhaps directly described object is back to applet through service end stake and client stake successively.
The present invention by client stake and the transparent request of transmitting Applet to server object of service end stake, has not needed special monitoring service by owing to adopted the adapter of lightweight; Solve complexity and difficult debugging that simple Applet directly calls; Owing to adopted the two-stage buffering, improved the speed of handling; Adopt real-time buffer object life cycle management, dynamic buffering object, the disposal ability of raising framework; The object of request carries out the privately owned and publicly-owned target buffer mechanism of object by the type of request; Carry out the life cycle management of object by the frequency that is called recently of publicly-owned object, the memory size of object, the average time of implementation of object and the initial time of object.
Description of drawings
Fig. 1 is the networking diagram of prior art one described method;
Fig. 2 is the networking diagram of prior art two described methods;
Fig. 3 is the method for the invention flow chart;
Fig. 4 is one embodiment of this invention system group network figure;
Fig. 5 is another embodiment of the present invention system group network figure;
Fig. 6 is an intelligent scheduler system construction drawing of the present invention;
Fig. 7 is the another kind of intelligent scheduler system construction drawing of the present invention.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, below in conjunction with embodiment and accompanying drawing, the present invention is described in more detail.
Consult shown in Figure 3ly, the present invention is provided with a lightweight adapter between Applet end and Web service end object, and the lightweight adapter is divided into client stake and service end stake; When Applet initiates call request to server, be responsible for tackling this request by the client stake, and by built-in tunnel the service end stake submitted in request, this built-in tunnel is based on the connected mode of Http; The service end stake passes to Web server to request, by controller described request is dispatched, and this controller can be arranged on the Web server or with Web server and link to each other.Can carry out calling of service end object according to corresponding regulative strategy by the stake of client stake Connection Service end, and manage various objects according to certain strategy.
Client stake and service end stake are the stakes of a lightweight, generate according to object, and accessed object is encapsulated.The client stake that encapsulates has identical interface with accessed object.The service end stake belongs to passive type and triggers, and utilizes the monitoring of existing Web server end container, is triggered by the monitor of Web container and calls the service end stake, need not to set up another port and monitors.The mode that generates described stake and encapsulation is a lot, can adopt the generating mode of similar existing EJB stake (enterprise-level Javabean stake).Client stake and server end stake can be generated automatically by the supporting small tool of framework, also can be write as according to the coding of request is manual.The client stake is encoded to request, and the service end stake is decoded to request, and itself does not offer port the service end stake, relies on the existing servlet Servlet of WEB service end controller fully and dispatches.Need to offer specially listening port and monitoring service in the prior art by adopting the lightweight adapter to solve, reach complexity and difficult problem of debugging that simple Applet directly calls, lowered visit WEB service object's complexity and fallibility simultaneously.
In order further to improve processing speed, intelligent scheduler, private object pond, publicly-owned object pool are set, as shown in Figure 4 between service end stake and WEB server.
Setting up the private object pond deposits the far call person transfers object accordingly, it generally is status object, the size in private object pond determines that according to different application the object life cycle in the private object pond can dispose, and can dispose the time value of an optimum according to different application.Publicly-owned object pool keeps the Web container to be cushioned by the common object of far call, be equivalent to level 2 buffering, the size of object pool is relevant with concrete application, come the nearest invoked frequency of the frequency that is called, the memory size of object, object of tracing object, the average time of implementation of object or the initialization time of object according to intelligent scheduler, whether decision objects continues is kept in the object pool.
Intelligent scheduler has two important function, and a function is the life cycle of object in the publicly-owned object pool of monitoring; Another function is the request of rational management client, abandons request or request is passed through other servers according to the actual loading of service end and selection of configuration, to realize the load balancing of a lightweight.
Intelligent scheduler can be provided with time-out time for the private object pond, promptly the object in the private object pond is not done relevant calling as far call in the some time, then deletes all objects and object pool itself.Intelligent scheduler also can upgrade the corresponding object of preserving in the private object pond according to the attribute that calls of each object in the private object pond.Can life cycle be set to each object in the private object pond as intelligent scheduler, in this life cycle, a certain object is then deleted this special object not by far call in the private object pond.Indexs such as invoked frequency of the object that respectively is called that intelligent scheduler regularly returns according to intelligent scheduler or object size are upgraded the object in the publicly-owned object pool.
When Applet initiates call request, described request is carried the destination object that will ask, the request of Applet is at first by client stake interception, and the client stake passes to long-range service end stake to request by connecting the tunnel, by the service end stake request is passed to intelligent scheduler again; Whether intelligent scheduler is judged from the object of client-requested in the private object pond, and is carried out following processing according to the result:
(1) if object in the private object pond, just obtains object and returns to the service end stake from the private object pond, by the client stake object is returned to Applet by the service end stake again.
(2) if object not in the private object pond, intelligent scheduler detects from publicly-owned object pool whether available object is arranged, and carries out following processing according to testing result:
If the A intelligent scheduler finds in the publicly-owned object pool available objects is arranged, then can be according to the information decision processing mode of solicited message or available objects.As object being moved on in the private object pond, obtain object by the private object pond and return to the service end stake, by the client stake object is returned to Applet by the service end stake again; Also can directly available objects be obtained object and return to the service end stake, by the client stake object be returned to Applet by the service end stake again by publicly-owned object pool.
If the B intelligent scheduler finds also there is not available objects in the publicly-owned object pool, then intelligent scheduler is directly dispatched Web server, obtain available objects after, according to the information of solicited message or available objects decision processing mode.Can be put in the publicly-owned object pool after with described object initialization by intelligent scheduler, directly available objects be returned to the service end stake, again give Applet by the client stake with object by the service end stake again by publicly-owned object pool; Also can directly described available objects be positioned over the private object pond, will obtain object by the private object pond again and return to the service end stake, by the client stake object be returned to Applet again by the service end stake again by scheduler; Can also directly object be back to the service end stake by intelligent scheduler, by the client stake object be returned to Applet by the service end stake again.
The call request that Applet initiates can be carried request type, mainly includes three types of state, stateless and acquiescences.The client foundation needs the appointed object state, and described state is carried in the call request of Applet initiation.If request type is that state is arranged, then requested object must be put into the private object pond, and carry out searching earlier when object is searched the private object pond; If request type is a stateless, then requested object must be put into publicly-owned object pool; If request type is acquiescence,, decide processing as initialization time of object memory size, object etc. then according to the attribute of object itself.
For load balance, can adopt many WEB servers, as shown in Figure 5.Linked to each other with intelligent scheduler by two WEB servers among Fig. 5, every is provided with corresponding target buffer threshold values.When the wherein a certain station server of a plurality of client-requested, intelligent scheduler judges that the object scheduling request of this WEB server surpasses this target buffer threshold values, then just described request is transmitted to another server process, reaching load balancing, thereby increases the throughput of whole system.Wherein, described target buffer threshold values can be to the WEB server dispatch request, surpass a certain numerical value to the dispatch request of the publicly-owned object pool of WEB server or to the dispatch request in private object pond etc.
After the request of intelligent scheduler acceptance from client, can also determine whether accepting described request according to current actual loading and the server limit load amount that sets in advance, if server load has surpassed the server limit load amount that sets in advance, then will abandon described request.
The present invention discloses a kind of intelligent scheduler, and as shown in Figure 6, it comprises that client-requested receiver module, object search module, publicly-owned object pool administration module, private object pond administration module, wherein,
The client-requested receiver module is used for linking to each other with the service end stake, receiving the call request that Applet initiates, and described request is forwarded to object searches module;
Described object is searched module and is used for linking to each other with WEB server, publicly-owned object pool, private object pond and service end stake, receive the request that the client-requested receiver module is transmitted, search private object pond, publicly-owned object pool or WEB server according to request, lookup result is forwarded to publicly-owned object pool administration module or private object pond administration module;
It is mutual that private object pond administration module is searched module with object, accept operation and management that lookup result carries out the private object pond, described operation and management comprise, the described request object is put into the private object pond, object is removed from the private object pond, described object is sent to the service end stake, the life cycle of described object or the life cycle in private object pond etc. are set;
It is mutual that publicly-owned object pool administration module is searched module with object, accept operation and management that lookup result carries out publicly-owned object pool, described operation and management comprise, the described request object is put into publicly-owned object pool, object is removed, described object is sent to the service end stake, the life cycle of described object or the life cycle in private object pond etc. are set from publicly-owned object pool.
Described object is searched module also can be forwarded to request the service end stake.
The present invention also discloses a kind of intelligent scheduler, and as shown in Figure 7, it comprises that client-requested receiver module, object search module, request processing module, publicly-owned object pool administration module, private object pond administration module, scheduling strategy module, wherein,
The client-requested receiver module is used for linking to each other with the service end stake, receiving the call request that Applet initiates, and described request is forwarded to the scheduling strategy module;
Described object is searched module and is used for linking to each other and the service end stake with WEB server, publicly-owned object pool, private object pond, the query statement that the receiving scheduling policy module issues, search private object pond, publicly-owned object pool or WEB server according to instruction, lookup result is forwarded to scheduling strategy module, publicly-owned object pool administration module or private object pond administration module;
The scheduling strategy module is used for searching module with object, the client-requested receiver module, publicly-owned object pool administration module, private object pond administration module, request processing module links to each other, receive the call request that connection module sends according to client-requested, according to the configuration parameter that sets in advance to this processing of request mode, as abandon request, to ask transparent transmission to other servers, and the described processing mode of foundation is searched module to object, request processing module issues searches or processing command accordingly, and searches module according to object, the process information that request processing module is returned is back to private object pond administration module and publicly-owned object pool administration module;
Request processing module links to each other with the scheduling policy module, accepts the processing instruction that the scheduling strategy module issues described request is handled;
Private object pond administration module searches module with object and the scheduling strategy module is mutual, accepts the instruction carrying out of lookup result and the scheduling strategy operation and the management in private object pond;
Publicly-owned object pool administration module searches module with object and the scheduling strategy module is mutual, accepts the instruction carrying out of lookup result and the scheduling strategy operation and the management of publicly-owned object pool.
Described object is searched module also can be forwarded to request the service end stake.
Claims (11)
1. the implementation method of an application program access Web server end object, it is characterized in that, a lightweight adapter is set between applet and Web server, and the lightweight adapter is divided into client stake and service end stake, and described method comprises the steps:
A, applet are initiated call request to the Web server end;
B, client stake interception applet are submitted to the service end stake to request to the request of server and by built-in tunnel;
C, service end stake are passed to Web server with described request, by the controller of Web server end according to request, whether the object of determining call request leaves in the private object pond that sets in advance, if, then from the private object pond, obtain object and make it be back to applet via service end stake and client stake;
If not in the private object pond, search in the publicly-owned object pool that sets in advance and whether deposited available objects, if have, then make this object be back to applet by service end stake and client stake, if do not have, directly the scheduling Web server obtains available objects, and makes this object be back to applet through service end stake and client stake.
2. the method for claim 1 is characterized in that, step B comprises that further the client stake encodes to request, and the service end stake is submitted in the request behind the coding; Step C further comprises after the service end stake is decoded to described request described request is passed to Web server.
3. the method for claim 1, it is characterized in that, in step C, after obtaining available objects from publicly-owned object pool, directly this available objects is back to applet via service end stake and client stake by publicly-owned object pool, perhaps, earlier this object is moved on in the private object pond, obtain object and be back to applet through service end stake and client stake by the private object pond;
Perhaps, in step C, after obtaining available objects from Web server, to be put in the publicly-owned object pool after this object initialization, directly available objects is back to applet through service end stake and client stake successively by publicly-owned object pool, or directly described available objects is positioned over the private object pond, will obtain object by the private object pond again and be back to applet through service end stake and client stake successively, or directly object will be back to applet through service end stake and client stake successively.
4. the method for claim 1 is characterized in that, carries the request type of client appointment in the call request that the described applet of steps A is initiated, and step C further comprises according to request type and carries out request scheduling.
5. method as claimed in claim 4 is characterized in that the described request type includes state, stateless, acquiescence; Step C dispatches further described request and comprises:
When the described request type is when state is arranged, requested object is put into the private object pond;
When the described request type is stateless, requested object is put into publicly-owned object pool;
When the described request type is acquiescence, according to the attribute decision processing mode that is requested object.
6. the method for claim 1, it is characterized in that, among the step C, also comprise: the controller of Web server end is according to the actual loading of Web server, and the Web server limit load amount that has set in advance, whether decision abandons described request or it is changeed by other Web servers processing.
7. the method for claim 1, it is characterized in that publicly-owned object pool deposits that corresponding object comprises further that publicly-owned object pool is called recently according to Web server end object whether average time of implementation of memory size, object of frequency, object or the initialized time decision of object put into publicly-owned object pool with object or with its deletion.
8. the method for claim 1, it is characterized in that, the private object pond is deposited corresponding object and further is included as the private object pond life cycle is set, if far call does not call the object in the private object pond in this life cycle, then delete all objects, comprise object pool itself; Or upgrade the corresponding object of preserving in the private object pond according to the attribute that calls of each object in the private object pond.
9. the method for claim 1 is characterized in that, the described controller of step C is meant the Servlet of Web server end inside or is independent of third party's scheduler of Web server end.
10. an intelligent scheduler is characterized in that, described scheduler comprises that client-requested receiver module, object search module, publicly-owned object pool administration module and private object pond administration module, wherein,
The client-requested receiver module is used for linking to each other with the service end stake, receiving the call request that applet is initiated, and described request is forwarded to object searches module;
Described object is searched module and is used for same Web server, publicly-owned object pool and private object pond and links to each other, receive the request that the client-requested receiver module is transmitted, search private object pond, publicly-owned object pool or WEB server according to request, lookup result is forwarded to publicly-owned object pool administration module or private object pond administration module;
It is mutual that private object pond administration module is searched module with object, accepts operation and management that lookup result carries out the private object pond;
It is mutual that publicly-owned object pool administration module is searched module with object, accepts operation and management that lookup result carries out publicly-owned object pool;
Whether the object that described intelligent scheduler is judged described call request in the private object pond, if in the private object pond, then obtains described object, and makes described object be back to applet via service end stake and client stake successively from the private object pond;
If not in the private object pond, then search described object whether in publicly-owned object pool, if in publicly-owned object pool, then described object is back to applet via service end stake and client stake by publicly-owned object pool, perhaps earlier described object is moved on in the private object pond, obtain object and be back to applet through service end stake and client stake by the private object pond;
If not in publicly-owned object pool, then obtain described object from the WEB server, will be put in the publicly-owned object pool after the described object initialization, by publicly-owned object pool described object is back to applet through service end stake and client stake successively; Or described object is positioned over the private object pond, by the private object pond described object is back to applet through service end stake and client stake successively again; Perhaps directly described object is back to applet through service end stake and client stake successively.
11. an intelligent scheduler is characterized in that, described scheduler comprises that client-requested receiver module, object search module, request processing module, publicly-owned object pool administration module, private object pond administration module and scheduling strategy module, wherein,
The client-requested receiver module is used for linking to each other with the service end stake, receiving the call request that applet is initiated, and described request is forwarded to the scheduling strategy module;
Described object is searched module and is used for same Web server, publicly-owned object pool and private object pond and links to each other, the query statement that the receiving scheduling policy module issues, search private object pond, publicly-owned object pool or WEB server according to instruction, lookup result is forwarded to scheduling strategy module, publicly-owned object pool administration module or private object pond administration module;
The scheduling strategy module is used for searching module, client-requested receiver module, publicly-owned object pool administration module, private object pond administration module, request processing module with object and links to each other, receive the call request that connection module sends according to client-requested, determine this processing of request mode, issue processing instruction to object according to described processing mode and search module or request processing module, and accepting object is searched the process information that module or request processing module return and is sent to private object pond administration module or publicly-owned object pool administration module;
Request processing module links to each other with the scheduling policy module, accepts the processing instruction that the scheduling strategy module issues described request is handled;
Private object pond administration module searches module with object and the scheduling strategy module is mutual, accepts the instruction carrying out of lookup result and the scheduling strategy operation and the management in private object pond;
Publicly-owned object pool administration module searches module with object and the scheduling strategy module is mutual, accepts the instruction carrying out of lookup result and the scheduling strategy operation and the management of publicly-owned object pool;
Whether the object that described intelligent scheduler is judged described call request in the private object pond, if in the private object pond, then obtains described object, and makes described object be back to applet via service end stake and client stake successively from the private object pond;
If not in the private object pond, then search described object whether in publicly-owned object pool, if in publicly-owned object pool, then described object is back to applet via service end stake and client stake by publicly-owned object pool, perhaps earlier described object is moved on in the private object pond, obtain object and be back to applet through service end stake and client stake by the private object pond;
If not in publicly-owned object pool, then obtain described object from the WEB server, will be put in the publicly-owned object pool after the described object initialization, by publicly-owned object pool described object is back to applet through service end stake and client stake successively; Or described object is positioned over the private object pond, by the private object pond described object is back to applet through service end stake and client stake successively again; Perhaps directly described object is back to applet through service end stake and client stake successively.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2005100593169A CN1842071B (en) | 2005-03-28 | 2005-03-28 | Realization method and apparatus for application program access Web server end object |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2005100593169A CN1842071B (en) | 2005-03-28 | 2005-03-28 | Realization method and apparatus for application program access Web server end object |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1842071A CN1842071A (en) | 2006-10-04 |
| CN1842071B true CN1842071B (en) | 2010-06-23 |
Family
ID=37030915
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2005100593169A Expired - Fee Related CN1842071B (en) | 2005-03-28 | 2005-03-28 | Realization method and apparatus for application program access Web server end object |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1842071B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108270751A (en) * | 2016-12-30 | 2018-07-10 | 阿里巴巴集团控股有限公司 | Application management method, device and data sending processing method and apparatus |
| CN109639636B (en) * | 2018-11-06 | 2021-04-02 | 创新先进技术有限公司 | Service data forwarding method, service data processing method, service data forwarding device, service data processing device and electronic equipment |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1512707A (en) * | 2002-12-27 | 2004-07-14 | �Ҵ���˾ | Surrogate server, access control method and access control program |
-
2005
- 2005-03-28 CN CN2005100593169A patent/CN1842071B/en not_active Expired - Fee Related
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1512707A (en) * | 2002-12-27 | 2004-07-14 | �Ҵ���˾ | Surrogate server, access control method and access control program |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1842071A (en) | 2006-10-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101605056B (en) | J2EE server monitoring device and monitoring method employing same | |
| CN103560943B (en) | Network analytic system and method supporting real-time mass data processing | |
| Da et al. | Kalimucho: middleware for mobile applications | |
| CN108270818A (en) | A kind of micro services architecture system and its access method | |
| EP0861471A1 (en) | Registry communications middleware | |
| CN1191350A (en) | Apparatus and method for processing servlets | |
| CN104052759A (en) | System for realizing add-and-play technology of internet of things | |
| CN107025222A (en) | A kind of distributed information log acquisition method and device | |
| CN101997854A (en) | Processing system and method for providing data service | |
| CN112615746B (en) | Edge calculation method, device and system | |
| CN112313627B (en) | Mapping mechanism of event to serverless function workflow instance | |
| CN109743192A (en) | A kind of container cluster configuration management method and device | |
| CA2280492A1 (en) | Mobile communication method | |
| CN102148736A (en) | Method and system for fusing machine-to-machine (M2M) service platform and next generation service network | |
| CN108415689A (en) | Software sharing method based on the assembly of ubiquitous object three-stage | |
| CN1842071B (en) | Realization method and apparatus for application program access Web server end object | |
| CN1972276B (en) | A management method and system for protocol access | |
| CN101924815A (en) | 3G MOA phone middleware embedded system | |
| CN104009866B (en) | WEB network management systems Modular implement method and device based on RIA | |
| CN106021544A (en) | Distributive connection pool management method and system for databases | |
| CN1567835A (en) | Distributed cluster service management system and service management method in intelligent network | |
| CN109525443B (en) | processing method and device for distributed pre-acquisition communication link and computer equipment | |
| CN100440802C (en) | Service gridding system and method for processing operation | |
| CN115796758A (en) | Factory rule management platform | |
| CN115086311A (en) | Management system of enterprise cross-system service based on cloud service bus |
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 | ||
| ASS | Succession or assignment of patent right |
Owner name: TINNO MOBILE TECHNOLOGY CORP. Free format text: FORMER OWNER: HUAWEI TECHNOLOGY CO., LTD. Effective date: 20140604 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 518129 SHENZHEN, GUANGDONG PROVINCE TO: 518053 SHENZHEN, GUANGDONG PROVINCE |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20140604 Address after: 4, A, building 518053, building H-3, East China Town, 1, Xiangshan East Street, Shenzhen, Nanshan District Patentee after: SHENZHEN TINNO MOBILE TECHNOLOGY CO., LTD. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: Huawei Technologies Co., Ltd. |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100623 Termination date: 20180328 |