WinGate SDK
Page tree
ConfigureSpace tools

Versions Compared

Old Version 16

changes.mady.by.user Adrien de Croy

Saved on

compared with

New Version Current

changes.mady.by.user Aaron Koolen-Bourke

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Talk discussion resolved

...

Package

A package consists of the files required for the package to function , and a cryptographically signed manifest file which is used to validate package files. Typically a package represents an entire product or system of functionality such as Web Proxy Filter product, Script Engine or Logging.  Packages typically contain executable module files (DLLs), help files, and/or other ancilliary files.

...

Modules can be loaded either in the WinGate Engine process (system service on Windows), or in the WinGate Management Console process, or both.

Info

Anchor
EntryPointDescription
EntryPointDescription
Packages have at least one Module called the Entry Point DLL which is the module loaded by the host framework (either WinGate process and/or WinGate Management Console process) and initialised via the Mandatory module functions.

Info

Modules can have dependency files which are specified in the Manifest file. Specifying a dependency in a manifest file does several things:

  • It ensures the file is protected against tampering by placing a hash of the file inside the signed manifest file. If the hash in the manifest doesn't match the hash of the file on disk, the module won't load.
  • It controls whether a file is synchronised between the WinGate Engine and WinGate Management Console. See Package Synchronisation for more information.

Component

Within a module you have components which are sets of common functionality that you register with WinGate. Although in practice there is normally only one component registered for each module, a module can register any number of components.

...