Patent classifications
G06F16/955
REST API Validation
Embodiments validate representational state transfer (“REST”) application program interfaces (“API”). Embodiments receive a REST API specification that provides information for a plurality of REST APIs and parse the REST API specification to extract, for each REST API, a corresponding Uniform Resource Locator (“URL”), and corresponding parameter names response codes and payloads. Embodiments convert the parsed REST API specification into a converted text file, the converting including parameter constraints and parameter default values. Embodiments then generate all possible combinations of test data for each REST API from the converted text file and perform one or more test operations on each of the combinations of test data.
MULTI-PART REQUEST FOR TRANSFERS
A request to separate a transfer into a plurality of parts may be received, the request defining a total amount and a total time period. A plurality of request for transfer links may be prepared. Each of the links may be associated with a different transfer time period, each transfer time period being less than or equal to the total time period. Each of the links may be associated with a separate transfer part amount, and a summation of the separate transfer part amounts may be equal to the total amount. A plurality of request for transfer links may be provided to a transferor device, each link allowing a transfer to fulfill the separate transfer part amount to be performed without requiring input of the separate transfer part amount or recipient information.
RESTFUL METHOD AND APPARATUS TO IMPORT CONTENT BY GEO-AWARE CONTENT CACHING SERVICE
Representational state transfer (REST) based geo-aware content transfer includes a REST server configured for receiving an application programming interface (API) request from a client device. The REST server obtains a upload universal resource locator (URL) targeting a caching server that is geographically closest to the client device, constructs an upload link containing the upload URL and a completion callback, and sends the upload link to the client device. The client device uses the upload URL to upload content to the caching server. The caching server interprets the completion callback to obtain a completion URL and, upon completion of content uploading, makes a REST API call using the completion URL. Responsive to the REST API call, the REST server executes an inbound operation to complete the uploading to a content management system and returns the content URL to the caching server which sends the content URL to the client device.
USER INTERFACES FOR SURFACING WEB BROWSER HISTORY DATA
Systems and methods are described that include generating a repository of metadata based on a plurality of webpages accessed and saved in a browser history of a web browser executing on a computing device, generating, based on the metadata, a history cluster including a portion of the plurality of webpages related to a topic where the history cluster generation is based on the source events and the access timestamps of the webpages in the portion, and assigning respective scores for the webpages in the portion. In response to a request to view browser activity associated with the topic, the systems and method may generate and display a history cluster listing for the topic where the history cluster listing includes visit listings associated with the webpages in the history cluster that are determined to have a score that meets a threshold score.
USER INTERFACES FOR SURFACING WEB BROWSER HISTORY DATA
Systems and methods are described that include generating a repository of metadata based on a plurality of webpages accessed and saved in a browser history of a web browser executing on a computing device, generating, based on the metadata, a history cluster including a portion of the plurality of webpages related to a topic where the history cluster generation is based on the source events and the access timestamps of the webpages in the portion, and assigning respective scores for the webpages in the portion. In response to a request to view browser activity associated with the topic, the systems and method may generate and display a history cluster listing for the topic where the history cluster listing includes visit listings associated with the webpages in the history cluster that are determined to have a score that meets a threshold score.
SYSTEMS AND METHODS FOR PROCESSING REQUESTS FOR REAL-TIME TRANSFERS OF RESOURCES
A computer-implemented method is disclosed. The method includes: receiving transfer parameters associated with a request for a first transfer of resources, the transfer parameters including an identifier of a designated transferor associated with the first transfer; determining that the transferor is eligible to access at least one protected data source based on the transfer parameters; generating a request message for the request including reference data for accessing the at least one protected data source; and providing, to a computing device associated with the transferor, the request message.
TRACKING LINK GENERATION USING A KEYBOARD APPLICATION
Systems and methods relating to a keyboard application on a mobile device are disclosed. The keyboard application generates a search query which it sends to a remote server. Data located based on the search query is received from the remote server. The data is associated with a record comprising a record identifier. The keyboard application associates a GUI element of the keyboard application with the record identifier. An input is received corresponding to selection of the GUI element. A unique tracking link is generated comprising a URI and an identifier associated with the selection of the GUI element. The URI is a deep link into an application that can execute on the mobile device. The unique tracking link is stored in a database in association with the record and user identifier and passed to the application to access content of the application.
SIMULTANEOUS APPLICATION SUPPORT OF MULTIPLE IDENTITY MANAGEMENT SYSTEMS VIA VIRTUAL WEB SERVERS
Simultaneous distributed application support of multiple identity management systems is provided through the use of virtual web server instances, which enable one identity management system, on physical servers already running a pre-existing web server instance, which enables a different identity management system. Further, an intelligent rules-based determination is implemented to determine whether to route an access request to either the virtual or pre-existing web server instance. Since the virtual web server instances are generated on the same physical server that executes the pre-existing web service instance, the the existing network flow (i.e., a single URL) and physical infrastructure is leveraged to create a simplified approach to managing the simultaneous use of multiple identity management systems across different distributed applications.
Using path-based indexing to access media recordings stored in a media storage service
A media storage service may store a plurality of copies of a same media recording in cloud DVR, one copy specific to one of a plurality of clients. The client may interact directly with the media storage service based on path-based indexing techniques for playback of the media recording. The client may send a request, including a path of a manifest file associated with the copy specific to the client, to the media storage service. The manifest file may include information indicating respective paths of one or more segments of the copy. The media storage service may identify and return the manifest file to the client. The media storage service may further receive requests from the client to access the segments of the copy. The requests may include the respective paths, based on which the media storage service may retrieve the segments for the client to play.
Using path-based indexing to access media recordings stored in a media storage service
A media storage service may store a plurality of copies of a same media recording in cloud DVR, one copy specific to one of a plurality of clients. The client may interact directly with the media storage service based on path-based indexing techniques for playback of the media recording. The client may send a request, including a path of a manifest file associated with the copy specific to the client, to the media storage service. The manifest file may include information indicating respective paths of one or more segments of the copy. The media storage service may identify and return the manifest file to the client. The media storage service may further receive requests from the client to access the segments of the copy. The requests may include the respective paths, based on which the media storage service may retrieve the segments for the client to play.