uft-2.0

This release includes more minor progress based on the previous release,
but it seemed like time to cross the 1.x/2.x line.

The protocol has been in need of clarity, so that markdown has been updated.

uft-1.11

Many minor updates to both POSIX and VM/CMS implementations.

The POSIX client now supports using a proxy which facilitates VPNs and privacy networks.

uft-1.10.8

This release is largely to resolve an issue with the Unix 'sf' client where it failed to interact with some UFT servers (though it did work with others).

uft-1.10.7

UFT 1.10.7 includes both POSIX and VM/CMS components.

This release includes minor updates to the z/VM implementation.
The Unix/Linux (POSIX) implementation adds an early NETDATA decoder for received files.
('rls' and 'rcv' scripts are very simplistic but functional)

uft-1.10.6

UFT 1.10.6 here includes both POSIX and VM/CMS components.

With this release, the z/VM and Unix/Linux implementations are aggressively aligned.
Both servers explicitly run UFT/2 (rather than the older UFT/1 protocol, implicitly or otherwise).

This release is still somewhat developmental.
UFT was inspired by IBM RSCS and IBM NJE and there remain several features of that suite which the POSIX implementation lacks and which the z/VM implementation needs to improve emulate better.

The goal of UFT is to provide the capabilities of NJE networking yet without proprietary NJE protocol, without the added topology work of an NJE point-to-point network, and without the need for a server (daemon) at all participating nodes.

uft-1.10.5

UFT 1.10.5 (as released here) includes both POSIX and VM/CMS components.

In recent months, the POSIX implementation has been trimmed for successful build.
Some functions which were previously under development have been deferred.
(Most of these have working counterparts in the VM/CMS implementation.)