Hopto Inc.

Eldad Eilam

Christoph Berlin

Sujay Sundaram

Systems and methods for account specific login throttling are provided. A user with a user account may submit a request to a server regarding download of an application onto one or more user devices associated with the server. The server may determine that the current load of request is more than it handle, assign a number to the request, and send a responsive message includes information about when the application will be made available to the user account for download. Once the allotted number is called and the server is ready to make the application available to the user account, the server may send notification to the user. account. The user may then download the application onto the one or more client devices associated with the user account.

Account-specific login throttling

Data including information regarding a display of the host device may be received. A display of a client device may correspond to the display of the host device. Information regarding the display of the host device may be received and evaluated to identify commands related to the display of the host device. The identified commands are encoded for a browser associated with the client device. A bitstream describing the display of the host device may be generated to incorporate the encoded commands. The bitstream may then be provided to a client device, where the display of the client device is rendered using a browser. As such, the display of the client device continues to correspond to the host device.

Client rendering

Methods and systems for personalization in a shared environment are provided. Information is stored in memory regarding the shared environment to which a plurality of users are provided with access. A plurality of files are also stored in memory. Each file is specific to one of the users and may be updated to include information regarding changes to a resource as made in a session associated with the user. Subsequent access by the user to the resource may be based at least in part on the updated file. For example, in some embodiments, a request may be received over a communication network; the request may concern a rollback for an identified user. A session associated with the identified user may then be restored based on a file associated with the identified user and including information regarding changes to the session associated with the identified user.

Personalization of shared resources

Systems and methods for file caching are provided. A remote session is established with a host device via a communication network that allows a client device to access resources hosted on the host device. Such resources may include a file hosted on the host device, though the file opened using an application at the client device. A connection between the host device and the client device may be detected as interrupted, thereby terminating the remote session. Information regarding the file may be cached in memory of the client device upon detecting that the connection has been interrupted. Upon reconnection or start of a new connection, the cached information may be used to update the file at the host device. In some embodiments, the cached file may be accessible to the client device while off-line.

File caching upon disconnection

Cloud-based personalization of shared resources

Data including information regarding a display of the host device may be received. A display of a client device may correspond to the display of the host device. Information regarding the display of the host device may be monitored for changes. When a change is detected, a movement of an image may be identified. Instructions may be generated regarding the changes to the display. A client device may process such instructions to incorporate the detected change while maintaining a remaining portion of the display. The instructions may include a motion vector command for the image movement and a command to fill in space vacated by the moving image. As such, the client device is not required to re-process and re-render an entire display where a change pertains to only a portion thereof.

Motion vectors for cross-platform display

Systems and methods for distributed file-sharing across personal devices are provided. Information is maintained in memory regarding multiple user devices associated with an authenticated user. The stored information may concern one or more files stored on each of the user devices. A request is received from a first user device associated with the authenticated user concerning access to a file. One or more of the other user devices may store a copy of the file. The user devices that store a copy of the requested file may be identified. A request is sent to the identified user devices, which may then provide one or more portions of the requested file to the requesting user device, which may then assemble the portions into a whole copy of the file.

Distributed file-sharing across personal devices

Client side detection of motion vectors for cross-platform display

Data including information regarding a display of the host device may be received. Such information may be used to identify one or more top-level windows in the host device display. Further, it is determined which of the top-level windows is currently active. The active top-level window may be determined to include a text caret and further, that the text caret is active such a keyboard display appears in a portion of the display of the client device. Instructions are generated for automatic adjustment of the remaining portion of the display of the client device based on the location of the text caret.

Cloud-based text management for cross-platform display

Systems and methods for touch-based hovering on remote devices are provided. A client device may include a touchscreen sensor capable of detecting that a user finger is within a predetermined distance from the touchscreen surface, but is not actually touching the touchscreen surface. When a user holds one or more fingers above a touch-enabled client device, the user fingers may be detected. Further, the screen coordinates of the fingers above the client device are determined. The coordinates, along with a command regarding a hover event, are sent to a host device with which the client device has an open remote session. The host device may execute the command in accordance with the coordinates to effect a hover event. Display instructions are sent from the host device to the client device, which generates a client device display including a hover event corresponding to that executed on the host device.

Touch-based hovering on remote devices

Display screen with graphical user interface icon

Data including information regarding a display of the host device may be received. A display of a client device may correspond to the display of the host device. Information regarding the display of the host device may be received and evaluated identify the images in the display. The identified images may be stored in memory and associated with a uniform resource locator (URL). A bitstream describing the display may be generated in which each image is referenced using the associated URL. The bitstream may then be provided to a client device, where rendering of the bitstream results in a display corresponding to the host device. Rendering the display may include retrieving the images associated with the URLs in the bitstream.

Growing community of inventors

San Jose, CA, United States of America

Eldad Eilam