...

Within a package you have modules that represent distinct parts of your package/product. If you require engine side functionality you will have a module that runs in the WinGate engine. If you need to present a user interface then you will also need a UI module. Each module shows up in the Modules panel of the WinGate Management Console and can be enabled or disabled by the administrator if the appropriate setting is in the manifest file for that module.

...

• Malware scanning of HTTP and email traffic by the WinGate engine.
• Monitoring of chat protocols like MSN Messenger and Google Chat.
• Global threat assessment that coalesces information from around the globe on a schedule to warn administrators of trending threats.
• WinGate Management Console UI modules for all three of these that display information to the user on their results.

In this example you would have a total of 6 modules in your package.

Component

Within a module you have components which are sets of common functionality that you register with WinGate. Although in practical terms practice there is typically normally one component registered for each module, a module can register more than one component if it wishes just like the Qbik Schema module which houses the components for both the engine and UI in one module.

...

• A general scanning interface that can scan a file or block of memory.
• Quarantine interface that other software can use as a general quarantine areamodules can use to quarantine their own data objects.

The global threat assessment module might expose interfaces for:

• Updating and inspecting the global threat information from it's configured servers
• Managing servers that the system uses so another WinGate module could register itself as a threat assessment server.