Client Message Pool for Microblog Memory Management

The patent segments message management into multiple components: a message pool for centralized storage, an index list for organized retrieval, and batch processing mechanisms. This segmentation allows the system to handle large volumes of messages by dividing them into manageable units rather than attempting to process all messages simultaneously in a single structure.

The patent introduces a message pool as an intermediary component between the server and the client terminal. This intermediary structure serves as a buffer that receives messages from the server, stores them temporarily, and provides organized access to the client, thereby enabling the client to handle large message volumes without directly managing all messages from the server.

The patent implements preliminary actions by first pulling and storing only the message index list in memory, rather than loading all message bodies immediately. The index list serves as a preliminary structure that organizes message information, allowing the system to retrieve only necessary message bodies on demand, thereby reducing initial memory occupation while maintaining efficient message handling capability.

The patent extracts the message index information from the full message data and stores it separately in the message pool. By separating the index list from the complete message bodies, the system can maintain a compact index structure in memory while storing only essential message data, thereby reducing memory occupation while preserving productivity.

The patent applies partial action by loading only the message index list initially and then selectively loading message bodies only when needed. Instead of loading all message bodies at once (excessive action), the system loads a partial set (index list) and retrieves additional message bodies on demand, thereby maintaining message data completeness while avoiding memory exhaustion.

The patent implements dynamic message loading where the system can adaptively retrieve message bodies based on user interactions and current needs. The message retrieval process is dynamic rather than static, allowing the system to adjust which message bodies are loaded into memory based on actual usage patterns, thereby maintaining data completeness while optimizing memory consumption.