VXNs are not meant to totally replace the need for or use of common CGI scripts. Rather, VXNs allow CGIs to be accessed far more easily then they were before. Traditional CGIs will still be necessary for some operations but VXNs will make many operations that called for CGIs far easier.
All VXNs are based on CGIs either written by Vaxxine or assimilated from another source. These CGIs are then installed in the normal manner. The sometimes painful issues of modifying source code and configuration files are completed during installation.
The CGIs are then enhanced to be able to work the same way under different conditions. For instance, some CGIs fail to function if installed for a WWW site that does not use a virtual host and then a virtual host is introduced. The same type of problem can occur if a secure server configuration is introduced. These problems are resolved here.
As well, various CGIs are not able to be used by more than one site due to fixed configuration information. This means that clients with more than one site are required to make changes every time they wish to the CGI. An obvious loss of productivity. The CGIs that work as VXNs are altered to avoid this situation.
Next, the CGI is enhanced to use the keywords from the easy to read VXN file. This is instead of requiring that the user provide information using one of the more complex methods CGIs often employ.
The able below list the command features offered by VXNs and CGIs as well as the requirements to implement them. The Yes/No answers are based on very high averages, if not absolutes.
| Feature/Requirement | VXN | Plain CGI |
|---|---|---|
| Source code modifications required | No | Yes |
| Ease of installation | N/A | No |
| Can be used by multiple sites without conflict | Yes | No |
| Easy to use configuration files | Yes | No |