Application Co-Development Block Locking for Consistent Editing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Concurrent application development by multiple users leads to issues such as overwriting and inconsistency due to multiple versions of the same block of code being edited simultaneously, with existing tools failing to address these challenges effectively.
Innovation Solution
A system and method that manages co-development by using a global store lock service to lock instances of a block when a user is editing it, ensuring only one user can edit at a time, and synchronizing changes across all instances, while considering user privileges and block activity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple users concurrently edit different instances of the same block of code, then collaborative development efficiency is improved, but data consistency deteriorates due to overwriting and multiple versions
Solution Approach 1:
The system performs preliminary locking of code blocks before users can edit them. When a user requests to edit a block, the system checks if it's already locked, and if not, acquires the lock beforehand. This prevents other users from editing the same block simultaneously, ensuring data consistency while allowing concurrent development on different blocks.
Solution Approach 2:
The patent introduces a lock management system as an intermediary between multiple users and the code blocks they want to edit. This mediator tracks which blocks are locked by which users and coordinates access requests, allowing collaborative development while preventing conflicts that would compromise data consistency.
2Ease of operation
If offline asynchronous development is used, then user flexibility is improved, but merging complexity increases and error susceptibility worsens
Solution Approach 1:
The system provides real-time feedback to users about the lock status of code blocks and the current editing state. Users can see which blocks are locked by whom and adjust their workflow accordingly. This feedback mechanism enables offline users to plan their edits around current lock states, reducing merging complexity and errors while maintaining flexibility.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
This disclosure relates to method and system for managing co-development of applications. The method includes receiving a request corresponding to a first user to edit a Graphical User Interface (GUI) of a development environment for an application. The application includes a plurality of pages, which includes a plurality of blocks. The method includes retrieving lock data of each of the plurality of blocks and a first set of user privileges associated with the first user. The lock data of each block includes a lock status. The method includes determining editability of the first user to each of the plurality of blocks based on the lock data of each of the plurality of blocks and the first set of user privileges. The method includes rendering the GUI on a first user device associated with the first user based on the determined editability.