Mobile performance: paginated history loading#181
Merged
Conversation
In Remote mode (mobile), when a session has messages (MessageCount > 0) but history hasn't been fetched yet (History.Count == 0), show a spinner with 'Loading conversation…' text instead of a blank chat area. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Mobile initially fetches only the 10 most recent messages per session, significantly reducing payload size and load time. A 'Load rest of conversation' button appears when the server has more history available. - GetHistoryPayload gains Limit field (null = all) - SessionHistoryPayload gains TotalCount and HasMore fields - Server respects limit, returning most recent N messages - Client tracks HasMore per session - ExpandedSessionView shows load-full-history button when HasMore is true Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The server was sending full history for ALL sessions on client connect, causing ~13s load time. Now sends only the 10 most recent per session. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Dramatically reduces mobile load time by paginating chat history over the WebSocket bridge. Previously the server sent full history for every active session on connect (~13s). Now it sends only the last 10 messages per session.
Changes
Bridge Protocol
GetHistoryPayloadgainsLimitfield (null = all messages)SessionHistoryPayloadgainsTotalCountandHasMorefieldsServer (
WsBridgeServer.cs)Client (
WsBridgeClient.cs)RequestHistoryAsyncaccepts optionallimitparameterSessionHistoryHasMoreper session from server responseUI (
ExpandedSessionView.razor)Testing
Known follow-ups from review