Mbedthis Appweb Release Notes
Welcome to the Mbedthis Appweb distribution. This document
describes the procedure for installing the binary Mbedthis Appweb
package. This package contains a pre-built stand-alone (binary)
web server and the development libraries and headers needed to
embed Appweb in a device or application. Once installed, you
may read the Appweb online documentation and samples for further
information. You can also read the documentation for the latest
release online at:
http://www.mbedthis.com/products/appweb/doc/index.html
This software is copyrighted and distributed under license. It
is available under an open source and a commercial licenses.
Please read the LICENSE.TXT for details.
System Requirements
Operating System Support
- Linux 2.4, 2.6 (x86,arm,ppc,sparc,xscale,mips) including
Redhat and Debian based distributions.
- Windows Vista, XP, 2000 (x86)
- VxWorks (x86,arm,ppc,sparc,xscale,mips)
Note the binary distributions are only made available for
X86 platforms.
Development Environment Hardware Platform Support
If you wish to build the samples or rebuild Mbedthis Appweb
from source code, you will need to use a C++ compiler and
associated development tools. Several development environments
are supported. You may choose any of the following to compile and
build samples and source code.
- Linux GNU tools
- Windows Visual Studio (Visual Studio 6 and Visual
Studio.NET 2005). This also requires the Cygwin UNIX emulation
tools. See www.cygwin.com.
Run-time System Requirements
To run Mbedthis Appweb, your system will need at least the
following resoures (depending on your configuration)
- 1 MB spare RAM memory
- 600 KB disk / ROM space
- TCP/IP network stack
To develop applications that use Mbedthis Appweb you will need
an additional
To rebuild Appweb from source code, you will need at least
PackagesAppweb
includes several packags including OpenSSL, MatrixSSL and PHP. These
packages have their own licenses. Appweb supports and includes two SSL
packages. Please note that MatrixSSL has a GPL license and if you wish
to use it in a commerical product, you may require a commerical license
from Peersec. OpenSSL may typically be used in either commerical or
open source based implementations. Make sure you check the packages
license details to ensure you are complying with their license.
Features
This release includes
support for the following features:
- HTTP/1.0 and HTTP/1.1 compliant HTTP server
- Apache style configuration
- Embeddable in single and multithreaded applications
- Embedded Server Pages (ESP)
- Embedded JavaScript (EJS)
- Embedded Gateway Interface (EGI)
- Common Gateway Interface (CGI)
- PHP5
- Digest and basic authentication
- File Upload
- Access and error logging streams
- Secure Sockets Layer (SSL) via OpenSSL and MatrixSSL
- Sandboxing environment for additional security
- HTTP client
- Extensible via dynamically loadable modules
- Samples
- Documentation
Release Build
This distribution is a RELEASE build and has little trace and
or debug assertions to help find bugs. If you rebuild from source
code, a DEBUG build may be created which has more trace to assist
in debugging. Performance with the DEBUG build will be slower and
the memory footprint will be larger than with the release
build.
Helpful Hints
Debug Trace and Logging
Appweb has a logging and trace facility that can help greatly
when diagnosing configuration issues or developing your
application code that uses Appweb. You can see what modules are
loaded and how, what requests arrive and how they are serviced.
You can also vary the level of logging via the appweb.conf
configuration file or via the -l logfile command line
switch. The log command line switch has the format
-l logFile:logLevel
where level can be from 0 to 9, with 9 being the most verbose
level. A level of 6 usually gives plenty of detail. You can
define the log file and log level via the appweb.conf file
using the ErrorLog and LogLevel directives.
Resolved Issues
See the new
features and fixes in the New
Features document.
|