Bureaucrats, editor
349
edits
Changes
Jump to navigation
Jump to search
no edit summary
* Pins (TO BE DONE)
** Currently it is same as UserTimestamp
* Recordings
** Cache time expires *** Because a recording is going to change state scheduled->ongoing, ongoing->finished*** Config (Configmaximum cache time)*** Changes in series are performed directly in VRM, or because a Recording so those changes its state)will not be reflected in the RecordingsTimestamp
** New recording Added
** Recording Cancelation
** Recording protection
* Rights (TO BE DONE)
** Currently it is same as UserTimestamp
* Services (TO BE DONE)
** Currently it is same as UserTimestamp
* Tags (TO BE DONE)
** Currently it is same as UserTimestamp
* Resumes
** With resumes.api active: New resume info added
** With resumes.api inactive: Equal to UserTimestamp
'''UserTimestamp changes when'''
* Purchase is made/cancelled
** gvp.gal (addMultipleSubscription, removeMultipleSubscription, addPpv, removePpv, extendRentalTime, cancelRental...)
** gvp.api (createPurchase, createPurchaseStb, CancelPRoduct)
* Tags changes
** gvp.api (TagProduct, TagItem, RemoveUserWatchHistory..)
* Services are activated/deactivated
** gvp.api(AcceptUserAgreement, RemoveServiceAgreement)
* Purchase status changes
** gvp.gal.productsintegration
* Pin is disabled
** gvp.api (disablepin, EnablePin not changing timestamp)
