[mythtv-commits] Ticket #11495: Patch to service api (dvr endpoint) allowing editing of existing recording schedules + backports dvr endpoint changes in trunk

[MythTV]

#11495: Patch to service api (dvr endpoint) allowing editing of existing recording
schedules + backports dvr endpoint changes in trunk
---------------------------------+----------------------------
 Reporter:  dev-team@…           |          Owner:  gigem
     Type:  Patch - Feature      |         Status:  closed
 Priority:  minor                |      Milestone:  unknown
Component:  Bindings - XML/JSON  |        Version:  0.26-fixes
 Severity:  medium               |     Resolution:  fixed
 Keywords:  services-api dvr     |  Ticket locked:  0
---------------------------------+----------------------------
Changes (by David Engel <dengel@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:2865936d776f42759e2b41ed152126b0b264eb32/mythtv]:
 {{{
 #!CommitTicketReference repository="mythtv"
 revision="2865936d776f42759e2b41ed152126b0b264eb32"
 Rework recording rule handling in services API.

 Thanks to tafy/dev-team%40tikinou.com providing the initial patch and
 testing the end result.

 The existing AddRecordSchedule() and new UpdateRecordSchedule() calls
 essentially take complete, fully-specified rules and sanity check them
 before saving.  AddRecordSchedule() is used to add new rules and
 UpdateRecordSchedule() is used to update existing rules.

 GetRecordSchedule() is changed to conveniently provide rules suitable
 for later calls to AddRecordSchedule() and UpdateRecordSchedule().
 When given a valid RecordId, GetRecordSchedule() returns that rule.
 When given a Template name, GetRecordSchedule() returns an empty rule
 initialized with that template.  When given a ChanId and StartTime,
 GetRecordSchedule() returns the rule for that program or a new one if
 no rule currently exists.  If the MakeOverride parameter is true, the
 returned rule for the program will converted to an override rule if
 needed.

 Clients should always call GetRecordSchedule() with the appropriate
 parameters before modifying the rule and then calling
 AddRecordSchedule() or UpdateRecordSchedule().  In this way, clients
 do not need to know all of the details on how to initialize rules or
 update them for specific programs.

 Fixes #11495
 }}}

-- 
Ticket URL: <http://code.mythtv.org/trac/ticket/11495#comment:2>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center