Private Communications Technology (PCT)
The process of bundling application components and related files in order to deploy them to a computer where they are available to users. These components can include COM components, Java classes, Web pages, and accompanying files. For example, you might package Java classes in a .cab file, and then deploy them to a Web server for downloading.
A performance optimization based on using collections of preallocated resources, such as objects or database connections. Pooling results in more efficient resource allocation.
Private Communications Technology (PCT)
A security protocol designed to provide privacy over the Internet. Like Secure Sockets Layer (SSL), PCT is intended to prevent eavesdropping on communications in client/server applications, with servers always being authenticated and clients being authenticated at the server's option. While an enhancement over SSL, secure PCT channels are often referred to as SSL.
An iterative, milestone-based approach to the development process. The way in which activities in a systems development life cycle are sequenced, and the time and formality committed to each life cycle stage. The combination of clearly defined life cycle model, project team roles, delivery milestones, and solution development principles.
In Remote Automation, an interface-specific object that packages parameters for that interface in preparation for a remote method call. A proxy runs in the address space of the sender and communicates with a corresponding stub in the receiver's address space.
In source control, an action to retrieve source changes from the source control server to the local machine. The ability to pull changes exists so that you can delay updating the local machine source control until files on the source control server (including files changed by others with access to the source control project) are in such a state that you can use them locally.
In source control, an action to send source changes to the source control server from the local machine. The ability to push changes exists so that you can delay updating the source control server until files on the local machine are in such a state that they can be used by others with access to the source control project.