WFS main features:
You do not need to compile the WFS. A precompiled version of the WFS can be found in the Barracuda Embedded Web Server's bin directory. Simply start this program from the command line, enter http://localhost:portnumber/ in a browser and read the introduction to the WFS. The WFS attempts opening port 80 and if this fails, the server attempt opening ports in the range 9357 - 9370. The server port number used by WFS is printed on the console.
This product includes:
Warning: the default WFS is designed for easy access and has no security. The WFS must, for this reason, run on a private network shielded from Internet access.
We recommend new users to view the WFS and the LSP Application Manager Videos. The LSP Application Manager requires the WFS when running in an embedded device without a file system.
The WFS can operate in four modes:
The WFS can operate as a file server for the NetIo HTTP client.
The NetIo file system was designed for developing web applications in embedded systems without a file system. The NetIo is also useful if you want to keep all web resources on your host operating system during development. All example programs delivered with the Barracuda Embedded Web Server SDK can be compiled/configured to use the NetIo client.
The LSP Application Manager can also load LSP applications via a NetIo. For more information, click the "More" button on the configuring the LSP Application Manager page.
The root URL to the WFS server is http://address/fs/. The URI /fs/ is the root for the WebDAV, the Web File Manager, and the NetIo server.
We recommend reading the product page for the WebDAV and the Web File Manager FuguHub plugins if you are new to WebDAV. The FuguHub Web Server is a consumer product designed using the Barracuda Embedded Web Server. FuguHub includes the same WebDAV and Web File Manager plugins as used in the WFS.
In addition to being used as a file server, the WFS can also load auxiliary LSP applications. LSP applications designed for the LSP Application Manager can also be loaded by the WFS, except examples that use the theme engine in the LSP Application Manager.
The difference between the LSP Application Manager and the WFS is that the LSP Application Manager is designed to run in any system, including firmware. The WFS can only be compiled on host like operating systems.
The following is the LSP Application Manager's Component Diagram.
The internals of the WFS is identical to the above diagram, except for the LSP Application Manager shown in red in the top left corner.
The Lua boot script .config stored in the embedded ZIP file is different from the LSP Application Manager. This script is what makes the WFS -- i.e. the Lua script is responsible for creating the Web File Server and the WebDAV server accessible at URI /fs/. The .config script is also responsible for loading auxiliary LSP applications.
C Startup Code:
The C startup code is different for the WFS as the startup code is specifically designed for being run on a host program. The C startup code extends the Lua VM and provides two global variables not found in the LSP Application Manager.
The WFS expects the two following environment variables to be set: TMP and HOME. The TMP directory is where the WebDAV locks are stored. The HOME environment variable is used when loading FuguHub applications that use SQLite databases. The database files are stored in the HOME directory.