-
- BlackBerry Dynamics
- Runtime library for iOS applications
- 12.0.1.79
Handler for AppKinetics consumer events. More...
#import <BlackBerryDynamics/GD/GDServices.h>
Responses to AppKinetics service requests are handled by creating a class that implements this protocol.
This class is part of the service consumer side of the AppKinetics programming interface.
The GDServiceClientDidReceiveFrom callback would be invoked after the application had sent a service request to a service provider, and the provider had responded or an error had occurred.
This class also includes a callback that is invoked when transmission of a service request completes.
The callbacks in this class will be invoked in the following sequence when a service response is received.
The first two of these callbacks enable the application to display a receiving status in its user interface. No action should be taken on any attachment files until the last callback, GDServiceClientDidReceiveFrom .
Instance Methods | |
| (void) | - GDServiceClientDidReceiveFrom:withParams:withAttachments:correspondingToRequestID: |
| AppKinetics service response callback. More... | |
| (void) | - GDServiceClientDidStartSendingTo:withFilename:correspondingToRequestID: |
| Service request file attachment transmission start callback. More... | |
| (void) | - GDServiceClientDidFinishSendingTo:withAttachments:withParams:correspondingToRequestID: |
| Service request transmission complete callback. More... | |
| (void) | - GDServiceClientWillStartReceivingFrom:numberOfAttachments:forRequestID: |
| Service response file attachments transmission start callback. More... | |
| (void) | - GDServiceClientWillStartReceivingFrom:attachmentPath:fileSize:forRequestID: |
| Service response individual file attachment transmission start callback. More... | |
|
required |
This callback is invoked when a response is received to an AppKinetics service request. The parameters give the details of the service response.
For an overall description of AppKinetics see the GDService class reference.
See under Callback Invocation Sequence, above, for the position of this callback in the order of service response callbacks.
A service response may be received in relation to a call to sendTo (GDServiceClient) that was accepted by the AppKinetics system.
The response can include file attachments and a results object from the provider application. Check the type of the results object to determine whether the service request succeeded.
If the results object is of type NSError then the service request failed. The error domain of the object will either be the GDServicesErrorDomain value, in the case of a generic AppKinetics failure, or a value that is specific to the service or to the provider application. In any case, the NSError object should have a suitable error code, a localizedDescription, and possibly additional data in its userInfo dictionary. See also the NSError class reference on the apple.com developer website for the full programming interface.
If the results object isn't of type NSError then the service request succeeded. In that case the results object will be of a valid service parameter type, as defined under Service Parameters in the GDService class reference.
| application | NSString containing the native application identifier of the provider application to which the original service request was sent. |
| params | The results object, as returned by the provider application. |
| attachments | NSArray of NSString objects containing the paths of files that were attached to the service response. See under File Attachments in the GDService class reference. |
| requestID | NSString containing the ID assigned to the original service request. An application that makes multiple concurrent service requests can use this value to tie the response back to the original request. The application must have retained the ID from when sendTo (GDServiceClient) was originally called. |
|
optional |
This callback is invoked when delivery of a service request file attachment by the AppKinetics system starts. The path of the file is passed as a parameter.
Invocation of this callback notifies the application that the AppKinetics system has started transferring the data in the file to the recipient of the service request.
The function that is invoked could display a sending status in its user interface. The sending status could be cleared on receipt of the GDServiceClientDidFinishSendingTo: callback.
| application | NSString containing the native application identifier of the recipient of the file. |
| filename | NSString containing the path in the secure store of the file that is now being sent. |
| requestID | NSString containing the unique identifier of the service request to which the file is attached. |
|
optional |
This callback is invoked when the delivery of an AppKinetics service request completes.
Invocation of this callback notifies the application that:
The function that is invoked can delete or modify any of the original file attachments, and free any resources used to hold the request parameters.
| requestID | NSString containing the unique identifier of the service request whose sending has completed. |
| attachments | NSArray of NSString objects containing the paths of any files that were attached to the service request. |
| params | Reference to the parameters object of the service request. |
| application | NSString containing the native application identifier of the application to which the service request was sent. |
|
optional |
This callback is invoked when file attachments are about to be received through the AppKinetics system. The number of files that are about to be received is passed as a parameter.
This callback will be invoked once per service response that has attachments. See under Callback Invocation Sequence, above, for its position in the order of service response callbacks.
The function that is invoked could display a receiving status in its user interface. The status could be cleared on receipt of the GDServiceClientDidReceiveFrom callback.
| application | NSString containing the native application identifier of the provider application that sent the service response to which the files are attached. |
| attachments | NSUInteger number of files that are about to be received, always one or more. This callback isn't invoked for service responses that have no attachments. |
| requestID | NSString containing the unique identifier of the original service request, the response to which the files are attached. |
|
optional |
This callback is invoked when an individual file attachment is about to be received through the AppKinetics system. The path and size of the file that is about to be received are passed as parameters.
This callback will be invoked once per attachment. See under Callback Invocation Sequence, above, for its position in the order of service response callbacks.
The function that is invoked could display or update a receiving status in its user interface. The status could be cleared on receipt of the GDServiceClientDidReceiveFrom callback.
| application | NSString containing the native application identifier of the provider application that sent the service response to which the file is attached. |
| path | NSString containing the path of the attachment. The value will be the same as one of the elements in the attachments parameter passed to the subsequent GDServiceClientDidReceiveFrom invocation. |
| size | NSNumber representing the size of the file in bytes. The value will be an unsigned long long. |
| requestID | NSString containing the unique identifier of the original service request, the response to which the files are attached. |