Java Method Remote Invocation via Message Passing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current technologies face challenges in efficiently calling Java methods across different Java Virtual Machines (JVMs) without pre-existing RMI service modules, limiting the ability to distribute load and perform calculations remotely.
Innovation Solution
A system and method that enables a server computer to transmit a message to a client computer for executing a Java method, with the client executing the method and returning the result, allowing for remote method invocation without the need for a dedicated RMI service module, utilizing a server-side message transmission section and client-side message reception, execution, and transmission sections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If RMI service module is used for remote method invocation, then Java methods can be called across JVMs, but the system complexity increases and requires pre-existing service modules
Solution Approach 1:
The patent extracts the core functionality of RMI (remote method invocation) from the complex RMI service module infrastructure and implements it through a simplified message transmission mechanism. The server transmits Java method source code as messages to clients, which execute the methods locally and return results, eliminating the need for pre-existing RMI service modules while maintaining remote invocation capability
Solution Approach 2:
The patent introduces a message as an intermediary carrier that transmits Java method source code from server to client. This message-based approach serves as a simplified mediator that replaces the complex RMI service module infrastructure, enabling remote method invocation through standard message transmission and execution mechanisms
2Productivity
If Java methods are executed on server, then centralized control is maintained, but server load increases and performance decreases
Solution Approach 1:
The patent segments the execution workload by transmitting Java method source code to multiple client terminals for local execution. This distributes the computational burden from the server to multiple clients, reducing server load and enabling parallel execution of methods across different terminals, thereby improving overall system productivity
Solution Approach 2:
The patent moves method execution from the server dimension to the client dimension by transmitting source code messages to client terminals. This dimensional shift in execution location allows clients to perform calculations locally using their own resources, significantly reducing server energy consumption and load while maintaining centralized control over which methods are executed
3Adaptability or versatility
If RMI service module is pre-installed, then remote method calling is enabled, but the ease of deployment and operation is reduced
Solution Approach 1:
The patent extracts the essential remote method calling functionality from the complex RMI service module requirement and implements it through a universal message transmission mechanism. This allows any system with message transmission capability to execute Java methods remotely without requiring pre-installation of specialized RMI service modules, greatly simplifying deployment
Solution Approach 2:
The patent creates a universal message-based execution mechanism that can operate across different platforms and systems without requiring specific RMI service module installations. The message transmission and execution approach serves multiple functions (method invocation, code distribution, result return) and works with standard communication infrastructure, enhancing ease of operation and deployment
Data Source
AI summary
A process and system for implementing a Java method. A browser in a second computer downloads, from a first computer, a web page having embedded therein a JavaScript and a Java applet. The second computer includes a Java Virtual Machine (JVM) communicatively coupled to the browser. After downloading the web page, the JavaScript receives from a Java servlet executing on the first computer a first message instructing the Java applet to execute the Java method. After receiving the first message, the Java applet executes the Java method. Executing the Java method includes the web browser executing the JavaScript which triggers execution of the Java applet by the JVM to cause executing the Java method by the Java applet. After executing the Java method, the JavaScript transmits to the Java servlet a second message that includes the Java method and a result of executing the Java method.