Glossary

Zero-Footprint

This term applies to those applications that don't require any client software to be installed or configured on a user's system. In other words, using a zero-footprint application assures that no trace is left of the session on the PC, either as temporary files or memory registries' values. In its most tight definition, zero-footprint also implies that the client code does not rely on calls to dynamic link libraries (DLLs) beyond those to standard operating system libraries. In the case of the e-Capsule™ client application, no calls are made to MFC DLLs, network libraries and run-time DLLs. Only standard APIs are used and linked only to comctl32, winsock2.dll and shell32.dll. All platform-dependent GUI elements (menus, toolbars, etc.) have been redesigned and rewritten as portable code. Use of third-party libraries is very limited and accepted only after the libraries are checked at the source code level and statically built into the e-Capsule™ code.