Local API Replicas for Server-Side Content Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The laborious and time-consuming process of uploading and testing executable content pages in a server environment hinders efficient development, as users must upload changes to test even minor edits, due to the inability to edit and test these pages locally with active REST calls.
Innovation Solution
Creating replica APIs on a local computing device that emulate the functionality of server-side APIs, allowing local testing and development of executable content pages with REST calls, eliminating the need for frequent uploads to the server environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If executable content pages are edited locally and then uploaded to the server environment for testing, then the ability to test changes is maintained, but the development process becomes laborious and time-consuming
Solution Approach 1:
The patent creates a local copy of the server environment by downloading executable content pages from the server to the local device. This copy can be edited and tested locally without affecting the server environment, eliminating the need for repeated upload cycles while maintaining testing capability
Solution Approach 2:
The patent segments the development process into local editing/testing phases and server deployment phases. By separating these functions, developers can work locally on copied files and only upload when ready for final deployment, reducing unnecessary upload operations
2Ease of operation
If executable content pages are allowed to be edited in the server environment, then local testing could be performed, but other users would be unable to access and use those pages in the active ERP system
Solution Approach 1:
The patent downloads a copy of the executable content page from the server environment to the local computing device. This copy can be freely edited and tested locally without impacting the version available to other users on the server, thus maintaining both local editing capability and user access availability
Solution Approach 2:
The local copy acts as an intermediary between the developer's editing needs and the server environment. Developers work on the local copy while the original server version remains unchanged and accessible to all users, resolving the conflict between editing access and user availability
3Ease of operation
If REST calls are made from locally edited executable content pages, then testing can be performed locally, but the calls fail because there is no authenticated session
Solution Approach 1:
The patent establishes an authenticated session with the server environment before local testing begins. The authentication token obtained from this preliminary action is stored and reused during local testing, enabling REST calls to function correctly without requiring a live server connection
Solution Approach 2:
The patent copies not only the executable content page but also the authentication context from the server environment to the local device. This includes storing authentication tokens and session information that enable REST calls to work locally without requiring an active authenticated session with the server
Data Source
AI summary
Computerized embodiments are disclosed that provide for testing an executable content page, normally run in a server environment, on a local computing device. In one embodiment, replica application program interfaces are stored on a hard drive of the local computing device in a local file at a same relative path location as corresponding application program interfaces stored in the server environment. The replica application program interfaces emulate the functionality of, and have the same names and arguments as, the corresponding application program interfaces. When an executable content page is executed on the local computing device for testing, representative state transfer (REST) calls may be made to the server environment via the replica application program interfaces stored on the local hard drive. In this manner, changes to an executable content page can be made and tested locally, without having to first upload the executable content page to the server environment.