Abstract: Systems and method of providing beacon-based notifications are provided. More particularly, an identifying signal can be received from a beacon device. A geographic location of a user device can be determined based at least in part on the identifying signal. At least a portion of time-based contextual beacon data can then be obtained based at least in part on spatial-temporal data associated with a user. One or more notifications associated with the contextual beacon data can then be determined. The one or more notifications can indicative of information corresponding to the beacon device, and can be provided for display on a user device.

Abstract: Systems and method of providing beacon-based notifications are provided. More particularly, an identifying signal can be received from a beacon device. A geographic location of a user device can be determined based at least in part on the identifying signal. At least a portion of time-based contextual beacon data can then be obtained based at least in part on spatial-temporal data associated with a user. One or more notifications associated with the contextual beacon data can then be determined. The one or more notifications can indicative of information corresponding to the beacon device, and can be provided for display on a user device.

Abstract: Systems and method of providing beacon-based notifications are provided. More particularly, an identifying signal can be received from a beacon device. A geographic location of a user device can be determined based at least in part on the identifying signal. At least a portion of time-based contextual beacon data can then be obtained based at least in part on spatial-temporal data associated with a user. One or more notifications associated with the contextual beacon data can then be determined. The one or more notifications can indicative of information corresponding to the beacon device, and can be provided for display on a user device.

Abstract: Systems and methods for adaptively scanning for one or more beacon devices based at least in part on user activity are provided. More particularly, a user device can scan for one or more beacon devices at a first scan rate. The user device can detect a trigger event based at least in part on data indicative of an activity level, such as data indicative of a status of a display, data determined from one or more motion sensors, a number of beacon devices detected by the mobile device during a time period, data indicative of prior interactions with beacon device information, or data indicative of a charging status of a battery associated with the mobile device. The trigger event can signify a change in an activity level associated with the user device. Responsive to the trigger event, the user device can adjust the scan rate from the first scan rate to a second scan rate.

Abstract: Systems and method of providing beacon-based notifications are provided. More particularly, an identifying signal can be received from a beacon device. A geographic location of a user device can be determined based at least in part on the identifying signal. At least a portion of time-based contextual beacon data can then be obtained based at least in part on spatial-temporal data associated with a user. One or more notifications associated with the contextual beacon data can then be determined. The one or more notifications can indicative of information corresponding to the beacon device, and can be provided for display on a user device.

Abstract: Systems and methods can secure against cross-site request forgery using client-side token storage. A client browser can initiate an action associated with a first web service and generate a token. The token may be stored in client-side storage at the computing device. An indicator of the action may also be stored within the client-side storage. A return link, associated with a passed copy of the token, may be generated. The client may perform the redirect and return to the first web service according to the return link. The passed copy of the token can be extracted from the return link. The indicator of the action and the stored token may be loaded from the client storage. The passed copy of the token and the stored token may be compared. The action according to the indicator of the action may be performed in response to the comparison matching.

Abstract: Systems and methods can secure against cross-site request forgery using client-side token storage. A client browser can initiate an action associated with a first web service and generate a token. The token may be stored in client-side storage at the computing device. An indicator of the action may also be stored within the client-side storage. A return link, associated with a passed copy of the token, may be generated. The client may perform the redirect and return to the first web service according to the return link. The passed copy of the token can be extracted from the return link. The indicator of the action and the stored token may be loaded from the client storage. The passed copy of the token and the stored token may be compared. The action according to the indicator of the action may be performed in response to the comparison matching.

Abstract: The present invention provides a method and system for achieving high availability in networked computer systems. The computer system includes a client node, two server nodes, and a secondary storage device. One server node includes a primary replica, and the other server node includes a secondary replica. In order for the client node to request a service that involves the secondary storage device, the client node sends a request for the service to the primary replica. The primary replica performs an intention phase of the service and sends a checkpoint message to the secondary replica. The secondary replica updates the state of the secondary replica and sends an acknowledgement message to the primary replica. The primary replica performs the service, sends a reply message to the client node, and forgets about the request. The client node resumes execution and asynchronously sends a forget message to the secondary replica. Upon receiving the forget message, the secondary replica forgets about the request.