Messenger Client Chat History Sync Across Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing instant messenger systems face challenges in maintaining synchronized message lists across multiple devices due to storage constraints and varying message retention policies, leading to inconsistent chat history displays when using different client devices.
Innovation Solution
A method involving a public repository for synchronizing messages between multiple messenger client devices, where local data is uploaded and merged with public data to ensure consistent display of previous chat lists across devices, independent of server involvement.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If messages are stored locally in each messenger client device, then storage constraints and security requirements are met, but message synchronization across multiple devices becomes inconsistent
Solution Approach 1:
A public repository acts as an intermediary between multiple messenger client devices, storing public data including previous chat lists. When a user logs into any device, the client downloads public data from the repository and merges it with local data to synchronize message history, ensuring consistency across all devices while maintaining local storage for security and performance
Solution Approach 2:
The message storage system is segmented into two parts: local storage for recent messages and private data, and public repository for shared previous chat lists. This segmentation allows each device to maintain its own local copy while periodically synchronizing with the public repository, resolving the contradiction between local reliability and global consistency
2Device complexity
If messages are stored on the messenger server for a predetermined period, then server management is simplified, but messages exceeding the period are lost and cannot be accessed on other devices
Solution Approach 1:
The public repository pre-stores previous chat lists and public data before they are needed by individual devices. When a user logs into any device, the data is already available in the repository for immediate download, eliminating the need for server-mediated message retention and ensuring message history availability independent of server storage policies
Solution Approach 2:
The system creates copies of message history data by storing them in the public repository. Instead of relying on the server to retain messages, multiple copies are distributed to the public repository, which then serves as a backup source that devices can access independently of server storage limitations
3Adaptability or versatility
If different devices use different message retention policies, then local storage requirements are optimized, but chat history display becomes inconsistent across devices
Solution Approach 1:
Each messenger client device is allowed to have its own local storage policy for managing recent messages and private data, while the public repository maintains a standardized copy of previous chat lists. This local quality approach allows devices to optimize their local storage independently while ensuring display consistency through synchronization with the public repository
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The disclosure relates to a method for synchronizing messages between a plurality of messenger client devices, and a messenger client device using the same, and the method for synchronizing messages between a plurality of messenger client devices to which a user account is shared according to an embodiment of the disclosure may include: accessing a pre-configured public repository and downloading public data including a previous chat list shared between the plurality of messenger client devices by a messenger client device; and generating merged data by merging the public data and local data including a previous chat list stored in a local repository of the messenger client device by the messenger client device.