17960058. EMBEDDING CODE FROM MODULES ACROSS VERSIONING BOUNDARIES simplified abstract (Microsoft Technology Licensing, LLC)
Contents
- 1 EMBEDDING CODE FROM MODULES ACROSS VERSIONING BOUNDARIES
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 EMBEDDING CODE FROM MODULES ACROSS VERSIONING BOUNDARIES - A simplified explanation of the abstract
- 1.4 Simplified Explanation
- 1.5 Potential Applications
- 1.6 Problems Solved
- 1.7 Benefits
- 1.8 Potential Commercial Applications
- 1.9 Possible Prior Art
- 1.10 Original Abstract Submitted
EMBEDDING CODE FROM MODULES ACROSS VERSIONING BOUNDARIES
Organization Name
Microsoft Technology Licensing, LLC
Inventor(s)
David Charles Wrighton of Redmond WA (US)
Anton Lapounov of Kirkland WA (US)
EMBEDDING CODE FROM MODULES ACROSS VERSIONING BOUNDARIES - A simplified explanation of the abstract
This abstract first appeared for US patent application 17960058 titled 'EMBEDDING CODE FROM MODULES ACROSS VERSIONING BOUNDARIES
Simplified Explanation
The computing system and method described in the abstract is focused on determining if a first software component has been updated when shipped separately from a second software component. This is achieved by copying a method from the first software component into the second software component, attaching it to metadata, and using this copy to validate that the original method has not been updated.
- Inline expansion process copies a method from the first software component into the second software component.
- The copied method is made executable when the corresponding method in the second software component is executed.
- The original method from the first software component is stored in metadata attached to the method in the second software component.
- The copy in the metadata is used to verify that the original method has not been updated.
Potential Applications
This technology could be applied in software development, particularly in ensuring the integrity and security of software components that are shipped separately.
Problems Solved
This technology solves the problem of verifying whether a software component has been updated after being shipped separately from another component.
Benefits
The benefits of this technology include enhanced security, integrity, and reliability of software components, as well as easier tracking of updates and changes.
Potential Commercial Applications
A potential commercial application of this technology could be in the development of secure software systems for industries such as finance, healthcare, and government.
Possible Prior Art
One possible prior art for this technology could be version control systems used in software development to track changes and updates in code repositories.
Unanswered Questions
How does this technology impact software development processes?
This technology could potentially streamline the process of verifying software updates and changes, leading to more efficient development cycles and improved software quality.
What are the implications of using metadata for validating software components?
Using metadata for validation could raise questions about data privacy, security, and the potential for unauthorized access to sensitive information. It would be important to address these concerns in the implementation of this technology.
Original Abstract Submitted
A computing system and method for determining if a first software component that has shipped separately from a second software component has been updated. An inline expansion process copies a first method of the first software component into a first method of a second software component is performed so that the copied first method is executable when the second method of the second software component is executed. The first method from the first software component is copied into metadata that is attached to the first method of the second software component. The copy of the first method in the metadata is used to validate that the first method in the first software component has not been updated.
