Abstract: A remote access application queries the client device for its display properties. Using the display properties of the client device and optionally the size of the fingertip of the user, a connection resolution for a remote desktop connection is determined. A remote desktop session is retrieved at the connection resolution and remote pixels are mapped to client pixels at a non-1:1 ratio. Remote desktop is then optionally resized to full screen.

Abstract: A remote access application queries the client device for its display properties. Using the display properties of the client device and optionally the size of the fingertip of the user, a connection resolution for a remote desktop connection is determined. A remote desktop session is retrieved at the connection resolution and remote pixels are mapped to client pixels at a non-1:1 ratio. Remote desktop is then optionally resized to full screen.

Abstract: A remote access application queries the client device for its display properties. Using the display properties of the client device and optionally the size of the fingertip of the user, a connection resolution for a remote desktop connection is determined. A remote desktop session is retrieved at the connection resolution and remote pixels are mapped to client pixels at a non-1:1 ratio. Remote desktop is then optionally resized to full screen.

Abstract: A computer draws an image by issuing an instruction to create a target HTML5 canvas, issuing an instruction to perform binary composition of a color of each pixel of at least a first portion of the target canvas and a color obtained from a color source such as a corresponding pixel of a source HTML5 canvas, issuing an instruction to paint a result of the binary composition onto at least a second portion of the target canvas, and rendering an image of the target canvas.

Abstract: In a client-server system, a server-node application runs a user session and a remote presentation protocol communicates between the client node and the server node. The server node stores a remote virtual desktop including remote windows of the user session. The client node displays multiple local windows of applications running locally on the client node and further displays one or more windows of the remote virtual desktop. The one or more windows are clipped to produce a clipped region so that the remote windows are displayed therein to appear as the local windows. The local windows are enumerated according to z-order from back to front and an area of each local window which overlaps the clipped region is subtracted from the clipped region so that the local windows show through the area.

Abstract: In a client-server system, a method providing windows of applications running on server nodes the same look and feel as windows of applications running on a client node, and providing remote virtual desktops with the same look and feel as the local desktop on the client node, including: (a) providing server nodes; (b) providing applications running on the server nodes; (c) providing a remote presentation protocol for accessing the applications; (d) providing at least one client node displaying windows of the applications on a local desktop; (e) communicating, to the server nodes, status information regarding attributes of the local desktop, by operating a first software module on the client node, the attributes including representational attributes and/or behavioral attributes, and (f) receiving the status information from the client node and applying the status information to the applications running on the server nodes, by operating a second software module on the server nodes.

Abstract: A method for single sign-on in a client-server system including a server and a client and a remote presentation protocol based on ITU T.120, communicates between the client node and the server. The client obtains a ticket for a user operating the client. The ticket identifies the security context of the user on the client. Upon connecting the client to the server, the ticket is transferred from the client to the server. The server authenticates the ticket with a security authority and when authenticated the server receives from the security authority a security context for the ticket. When the client so requests, applications are launched using that security context. Preferably, the server is a Microsoft Terminal Server and the remote presentation protocol is Microsoft Remote Desktop Protocol (RDP). The ticket transfer preferably uses a channel within the remote presentation protocol, such as an RDP virtual channel.

Abstract: In a client-server system, a server-node application runs a user session and a remote presentation protocol communicates between the client node and the server node. The server node stores a remote virtual desktop including remote windows of the user session. The client node displays multiple local windows of applications running locally on the client node and further displays one or more windows of the remote virtual desktop. The one or more windows are clipped to produce a clipped region so that the remote windows are displayed therein to appear as the local windows. The local windows are enumerated according to z-order from back to front and an area of each local window which overlaps the clipped region is subtracted from the clipped region so that the local windows show through the area.

Abstract: A method of, and system for, using a high-level, task-oriented Application Programming Interface (API) to access a legacy system, the method including the steps of: (a) providing the legacy system, including emulation software for accessing the legacy system; (b) operating a low level API over the emulation software; (c) operating the high-level, task-oriented application programming interface over the low level API, and (d) implementing database access protocol emulation over the high-level API.

Abstract: A method of, and system for, using a high-level, task-oriented Application Programming Interface (API) to access a legacy system, the method including the steps of: (a) providing the legacy system, including emulation software for accessing the legacy system; (b) operating a low level API over the emulation software; (c) operating the high-level, task-oriented application programming interface over the low level API, and (d) implementing database access protocol emulation over the high-level API.