Opened 14 years ago

Closed 14 years ago

#439 closed defect (invalid)

Server sends response to RESCHEDULE_RECORDINGS too quickly

Reported by: Derek Battams <derek@…> Owned by: Isaac Richards
Priority: major Milestone: unknown
Component: mythtv Version:
Severity: medium Keywords:
Cc: Ticket locked: no

Description

When sending the RESCHEDULE_RECORDINGS command to the server, it seems to send a response before it completes the reschedule leading to incorrect (out of date) information in response to a QUERY_GETALLPENDING issued immediately after the reschedule command. My remedy to the problem has been to sleep for 5 seconds after issuing the reschedule command, which works but isn't a guaranteed fix as some servers may have many more items to schedule than me and may need more time or for servers with fewer items then the 5 seconds seems like a waste. The best solution would be for the server not to respond until it has completed the reschedule.

Change History (3)

comment:1 Changed 14 years ago by Isaac Richards

Resolution: invalid
Status: newclosed

This is how it's supposed to work. The scheduler sends out a SCHEDULE_CHANGE message once it's done.

comment:2 Changed 14 years ago by anonymous

Resolution: invalid
Status: closedreopened

How is a (PHP) client suppose to receive that signal?

comment:3 Changed 14 years ago by Isaac Richards

Resolution: invalid
Status: reopenedclosed

How is it mythtv's bug if your client is not properly listening for messages?

Note: See TracTickets for help on using tickets.