Review draft

Download 423.93 Kb.

Page	10/16
Date	20.10.2016
Size	423.93 Kb.
	#6516

1 ... 6 7 8 9 10 11 12 13 ... 16

E.3.Package Interface

E.3.1.Access Event Subgroup

Components wishing to receive notification of account-related events must register as AccessEventListeners. While it is assumed that a Package will implement the AccessEventListener interface, this is not a requirement of the API

E.3.1.1.eventNotification()

Informs a registered listener of a change in content availability status, the completion of a user initiated request, or both. Changes to content availability may be due to a request from the consumer (e.g., a purchase) or may result from some event or action not initiated by the consumer (e.g., expiration of a rental period). If the change is derived from a consumer initiated request, any requestId provided when the acquire() method was invoked will be included in the event notification.

Any event notification associated with a request made via the acquire() method will also indicate the completion status of the request. In these cases the requestStatus field will be an integer value equal to one of the StatusDescriptor CODE_OP_xxxx values (see Section D.4.1).

Usage

eventNotification(String contentId, int[] eventCode, String requestId, int requestStatus)

Parameters:

contentId: the retailer’s content identifier

eventCode: the set of all applicable availability codes.

requestId: identifier associated with the request that resulted in the change to availability status (optional)

requestStatus: integer value equal to one of the CODE_OP_xxxx values (optional)

Returns: none

ECMAScript Example

Annex F. Account Access API Group

Account Access allows a package to access account properties, such as screen name, preferences and favorites as appropriate. It also provides the means to determine if the user is signed in. If appropriate, it can be used by the package to indicate that the user needs to sign in or sign out. The sign-in/sign-out procedures, like all other aspects of account management, are a retailer-specific process and are therefore handled by the framework.

Functionality to be implemented by the Framework is divided into the following subgroups:

Subgroup Summary
Basic	Methods to sign in or out and to access consumer preferences
Account Event	Interface to receive notification of account-related events

A Package will only implement the Account Event subgroup.

F.1.Framework Interface

F.1.1.Basic Subgroup

The role of the Framework instance is primarily to provide the package with access to user account data.

Method Summary
signIn	Opens the retailer’s sign-in UI.
signOut	Initiates the retailer’s sign-out process.
isSignedIn	Indicates if consumer is currently signed in.
getAccountProperties	Request for information regarding the properties of a signed-in consumer.
getPreferences	Request for information regarding the user interface preferences of a signed-in consumer.

F.1.1.1.signIn()

Opens the retailer’s sign-in UI. The specifics by which the consumer establishes their identity is up to the retailer. The sign-in process should be handled synchronously. Thus upon the completion of this method the returned StatusDescriptor will indicate the success or failure. No asynchronous event notification is associated with the sign-in process.

Usage

signIn()