[mythtv-firehose] mythtv/master commit: d4f718cd1 by Robert McNamara (rmcnamara)

MythTV noreply at mythtv.org
Fri Dec 2 00:25:17 UTC 2011


      Author:  Robert McNamara <rmcnamara at mythtv.org>
 Change Date:  2011-12-01T16:18:31-08:00
   Push Date:  2011/12/01 16:24:45 -0800
  Repository:  mythtv
      Branch:  master
New Revision:  d4f718cd132dd7014f0c903ffffdb32192e48ef6
   Changeset:  https://github.com/MythTV/mythtv/commit/d4f718cd1

Log:

Services: *** Make Services require UTC DateTime ***

PLEASE READ!

As MythTV will use UTC time internally in the near future, to
avoid disrupting initial adopters of the Services API,
adjust input and output of the API to require UTC.

What does this mean to current API users?  It means when
presenting the date to the user, you will need to translate
into local time.  It means the API will output times and
dates in UTC format, and you will need to input times and dates
in UTC format.  If you are getting all your data from the API,
then plugging that same data back in to other functions, your
application should require no modification aside from user-facing
strings.

What does it mean to MythTV devs?  It means that when Myth goes
to internal UTC datetimes, the code below will need to be partially
reverted, to remove the "toUTC()"s on output, and the "toLocalTime()"s
on input.  The user facing strings (HTML setup) should remain the same.

Modified:

   mythtv/html/misc/overview.qsp
   mythtv/html/samples/livestream_rec.qsp
   mythtv/html/samples/recorded.qsp
   mythtv/libs/libmythservicecontracts/service.cpp
   mythtv/libs/libmythtv/tv_play.cpp
   mythtv/libs/libmythupnp/serializers/jsonSerializer.cpp
   mythtv/libs/libmythupnp/serializers/xmlSerializer.cpp



More information about the mythtv-firehose mailing list