Abstract:
A venue-cast system and method for providing and receiving venue level transmissions and services, including discovery of a venue specific transmission by receiving an overhead signal from a non-venue network, extracting information for receiving the venue specific transmission from the overhead signal, and tuning to receive the venue specific transmission based on the extracted information. The venue level transmission may be provided and received in a manner that does not prevent an access terminal from receiving a local area or wide area transmission.
Abstract:
Commerce card techniques are described. In one or more implementations, one or more credentials are received at a commerce card, the credentials encrypted using a public key. The one or more credentials are decrypted using a private key that corresponds to the public key, the decrypting performed by a secure element implemented in tamper-resistant hardware of the commerce card without exposing the private key outside of the secure element. The decrypted one or more credentials are stored within the secure element of the commerce card such that the decrypted one or more credentials are not exposed outside of the secure element, the one or more credentials usable by the commerce card as part of a transaction to purchase a good or service.
Abstract:
The present systems and methods disclose a system for personalizing computer functionality. End-users are provided with tools to easily write rich and complex preferences, for example, by using a plurality simple IF-THEN propositional logic. The preferences are then transformed into queries and executed efficiently on structured data. Preferences that are satisfied then execute actions such as providing notification or storing data in a particular folder. Furthermore, according to an aspect of the invention, data, logic, events, inter alia, are all schematized, thereby enabling sharing of data between application components and across applications.
Abstract:
Various types of data can be collected into a data set and related content and/or related concepts across the data in the data set and/or across search histories can be displayed as a visual representation. The related content/concepts can be presented as a function of incremental revealing of relationships. After reviewing the visual representation, a user can customize the data set and relationships by specifically excluding a related data segment. The visual representation can be applied across multiple searches or other obtained data. Through interaction with the visual representation, a user can drill down into common linkages of the data to more narrowly focus on a subset of the data and/or to refocus a search result and/or to provide annotations.
Abstract:
The adaptive bandwidth throttling system implements a graceful diminution of services to the clients by delaying a first class of services provided by a network server in response to the effective bandwidth utilized by this network server exceeding a first threshold. If the demand for the bandwidth by this network server exceeds a second threshold, the bandwidth throttling system escalates the throttling response and blocks the first class of services from execution and can also concurrently delay execution of a second class of services. The implementation of the throttling process can be varied, to include additional levels of response or finer gradations of the response, to include subsets of a class of services. In addition, the threshold levels of bandwidth used to trigger the throttling response can be selected as desired by the system administrator.
Abstract:
The present invention relates to systems and methods to generate stored procedure calling code. The invention includes system and methods that utilize annotation(s) included in a stored procedure. The annotations comprise attributes that indicate the intent to have stored procedure calling code generated. After the annotated stored procedure becomes available, the code is compiled and, optionally, checked for errors, and an intermediate definition with metadata is created. The definition is a stored procedure interface language (SPIL) file. The SPIL definition is then utilized to generate high-level, stored procedure calling code, or class libraries. The high level code can then be employed within an application to invoke the stored procedure.
Abstract:
The adaptive bandwidth throttling system implements a graceful diminution of services to the clients by delaying a first class of services provided by a network server in response to the effective bandwidth utilized by this network server exceeding a first threshold. If the demand for the bandwidth by this network server exceeds a second threshold, the bandwidth throttling system escalates the throttling response and blocks the first class of services from execution and can also concurrently delay execution of a second class of services. The implementation of the throttling process can be varied, to include additional levels of response or finer gradations of the response, to include subsets of a class of services. In addition, the threshold levels of bandwidth used to trigger the throttling response can be selected as desired by the system administrator.
Abstract:
The adaptive bandwidth throttling system implements a graceful diminution of services to the clients by delaying a first class of services provided by a network server in response to the effective bandwidth utilized by this network server exceeding a first threshold. If the demand for the bandwidth by this network server exceeds a second threshold, the bandwidth throttling system escalates the throttling response and blocks the first class of services from execution and can also concurrently delay execution of a second class of services. The implementation of the throttling process can be varied, to include additional levels of response or finer gradations of the response, to include subsets of a class of services. In addition, the threshold levels of bandwidth used to trigger the throttling response can be selected as desired by the system administrator.
Abstract:
A server architecture includes a server program to receive a request from a client. In one aspect, an out-of-process application executing in a separate process from the server program is invoked to process the request and to generate a response to be returned to the client, and the server architecture includes a subsystem to detect when the out-of-process application fails and to recover the out-of-process application without disrupting operation of the server program. In another aspect, a method for detecting when an out-of-process application fails includes recording the request on a list as the request is passed to the application, examining the request as it is returned from the application, determining that the application has failed if the returned request contains erroneous data, and if the application has not failed then removing the request from the list.
Abstract:
A session manager has a session timeout mechanism to selectively timeout client-server sessions. The session timeout mechanism has multiple timeout buckets to hold corresponding groups of sessions according to the sessions' timeout periods. Sessions located in different ones of the timeout buckets are set to timeout at different times. The session manager also has a session timeout clock that is incremented every predetermined time unit (e.g., every minute). The session timeout clock maintains a pointer to one of the timeout buckets and advances that pointer with each clock increment. The session timeout clock advances the pointer through all of the timeout buckets, one bucket at a time. The session timeout clock advances the pointer repeatedly through all the buckets. The cycle time for the session timeout clock to reference every timeout bucket is equal to the incremental time unit multiplied by the number of buckets. A new session (or one that recently received a request and is restarting its timeout period) is inserted into a timeout bucket that is one or more buckets ahead of the clock pointer, depending upon the session's timeout period. When the timeout clock references a particular bucket, the sessions in that bucket are analyzed for possible timeout. Sessions whose timeout period has run without receiving any new requests are timed out and removed from the bucket.