Data context passing between non-interfaced application programs in a common framework
View Patent ↗Permitting the context sharing between non-interfaced web-based applications associated in a web-based framework server via adjusting the parent domain of the web-based applications and the framework to be the same, providing in the framework server the location of a JavaScript file, and configured to permit communication between the web-based applications through http function calls. The location of the JavaScript file may be provided to all the applications in the form of a cookie. Alternatively permitting context sharing between non-interfaced web-based applications associated in a web-based framework server comprising selectively adjusting the domain of the web-based applications and the framework such that each defines a subdomain of a parent domain when the web-based applications are being navigated.
1. A method for communicating between a plurality of non-interfaced web-based applications within a common browser framework comprising:
a framework server, in response to a user request, instructing a browser to create said common browser framework comprising a common parent framework domain, and a multiple of frames, each frame associated with an initially unique domain name of at least one of said plurality of non-interfaced web based applications;
further instructing said common browser framework to modify said common parent framework domain and each of said initially unique domain names and to form new domain names for each of said at least one web based applications wherein each new domain name is a sub-domain of said common parent framework domain, a second-level domain name of said common parent is a web server second-level domain name, and domain parameters of the at least one of non-interfaced web-based applications are modified at said framework server;
providing an executable program within said common browser framework configured to scan updated frame data and communicate said data between said multiple web based applications within said common browser framework;
providing a location within said common browser framework of said executable program to each of said multiple web applications; and
causing execution of said executable program.
2. The method of claim 1 wherein the common browser framework returns html content.
3. The method of claim 1 wherein the plurality of non-interfaced web-based applications are World Wide Web-based applications.
4. The method of claim 1 wherein the common browser framework is a thin framework.
5. The method of claim 1 wherein the common browser framework is a thick framework.
6. The method of claim 1 wherein the plurality of non-interfaced web-based applications are subdomains of a common parent domain on the server side.
7. The method of claim 1 wherein the plurality of non-interfaced web-based applications are accessed over an intranet.
8. The method of claim 1 wherein the plurality of non-interfaced web-based applications are accessed over the Internet.
9. The method in accordance with claim 1 wherein said modifying comprises changing each of said unique domain names into new domain names as follows:
using said first-level domain name of each of said web applications as a new first-level domain name;
using said second-level domain name of each of said web applications as a new third-level domain name;
selecting a common parent second-level domain name and using it as a new second-level domain name for each of said web applications.
10. The method in accordance with claim 1 wherein said executable program is written in the JavaScript language.
11. The method in accordance with claim 1 wherein location is provided to each of said multiple web applications as a cookie.
12. A method for communicating between a plurality of non-interfaced web-based applications within a common browser framework comprising:
a framework server, in response to a user request, instructing a browser to create said common browser framework comprising a common parent framework domain, and a multiple of frames, each frame associated with an initially unique domain name of at least one of said plurality of non-interfaced web based applications;
further instructing said common browser framework to modify said common parent framework domain and each of said initially unique domain names and to form new domain names for each of said at least one web based applications wherein each new domain name is a sub-domain of said common parent framework domain, the plurality of non-interfaced web-based applications are subdomains of a common parent domain on the server side, and domain parameters of the at least one of non-interfaced web-based applications are modified at said framework server;
providing an executable program within said common browser framework configured to scan updated frame data and communicate said data between said multiple web based applications within said common browser framework;
providing a location within said common browser framework of said executable program to each of said multiple web applications; and
causing execution of said executable program.
13. The method in accordance with claim 12 wherein said modifying comprises changing each of said unique domain names into new domain names as follows:
using said first-level domain name of each of said web applications as a new first-level domain name;
using said second-level domain name of each of said web applications as a new third-level domain name;
selecting a common parent second-level domain name and using it as a new second-level domain name for each of said web applications.
14. The method in accordance with claim 12 wherein said executable program is written in the JavaScript language.
15. The method in accordance with claim 12 wherein location is provided to each of said multiple web applications as a cookie.
16. The method of claim 12 wherein the common browser framework returns html content.
17. The method of claim 12 wherein the plurality of non-interfaced web-based applications are World Wide Web-based applications.
18. The method of claim 12 wherein the common browser framework is a thin framework.
19. The method of claim 12 wherein the common browser framework is a thick framework.
20. The method of claim 12 wherein the plurality of non-interfaced web-based applications are accessed over an intranet.
21. The method of claim 12 wherein the plurality of non-interfaced web-based applications are accessed over the Internet.