QEWS Questions and Answers

Public-domain implementations are often not be supported and maintained, and may not evolve with standards (e.g., CERN server).

In contrast, the application developer rather than the server developer makes the trade-offs when using QEWS. Quiotix's exclusive AutoSubset feature automatically creates a minimal server subset for each application. The application developer has the full range of server features available, but only those features actually used are included in the target environment.

First, the embedded web interface approach offers large development and support cost savings over the custom client approach. There is no need for extensive backward compatibility testing between server and client and no risk of having a management client that is too old or too new.

Second, QEWS's modular design allows developers to build applications without complex programming. Our exclusive AutoSubset eliminates the time-consuming and cumbersome task of reconfiguring and recompiling required by other embedded web servers. For most environments, QEWS is delivered in object code form, so developers don't even have to worry about compiling it.

Third, QEWS applications can be developed in a standalone mode, using the convenient development and debugging facilities of popular desktop environments (Windows, Unix, etc.) and using popular web-design tools (such as Adobe PageMill). Once the application is complete, the entire web interface can be automatically rehosted in the target environment. Files from the development environment, including web pages, images, Java applets, etc., can be incorporated directly into application, meaning that no file system access is required in the target environment.

In summary, QEWS is designed to maximize developer productivity, maximize software functionality, and minimize memory footprint. In all respects, QEWS outperforms other web servers hands down.