Opened 6 years ago

Last modified 2 years ago

#11798 new Developer Task

Allow asynchronous communication in backend protocol

Reported by: Raymond Wagner Owned by: Raymond Wagner
Priority: minor Milestone: 29.2
Component: MythTV - General Version: Unspecified
Severity: medium Keywords:
Cc: Ticket locked: no

Description

The communication between frontend and backend operates in one socket synchronously. One query cannot be asked before the previous query has responded. This can cause responsiveness issues when the UI thread blocks, waiting for access to the socket. Asynchronous communications could be added with limited disruption to third party clients by adding a new command that optionally enables it, and having all subsequent communications pass a message number immediately after the message size.

Change History (5)

comment:1 Changed 4 years ago by Karl Egly

Milestone: 0.28 → 0.29

comment:2 Changed 4 years ago by Stuart Auchterlonie

Milestone: 0.29 → 29.0

Milestone renamed

comment:3 Changed 2 years ago by Stuart Auchterlonie

Milestone: 29.0 → 29.1

comment:4 Changed 2 years ago by Stuart Auchterlonie

Milestone: 29.1 → 0.28.2

Moving remaining open tickets to 0.28.2 milestone

comment:5 Changed 2 years ago by Stuart Auchterlonie

Milestone: 0.28.2 → 29.2

Moving remaining open tickets to 29.2 milestone

Note: See TracTickets for help on using tickets.