|Licence||Not specified (open source)|
|Downloadable via the Homebrew Browser|
WiiBServer is a small and unfinished HTTP/1.0 server, used to test networking functions on the Wii. It loads resources from the front sd card.
I just wanted to play a little with networking functions on the wii so I started with something simple, the HTTP/1.0 protocol. Then I decided to try the sd card api and ended up with threads. Very interesting :-)
However, I won't work much on this project because:
- there's already another project of that kind
- the HTTP/1.1 protocol is far more complex to handle
- there's no real point in running a web server on the wii :-S
- there's already some specialized software for that (apache, ...), would be more interesting to port existing robust software
- I don't have enough time
Nothing special on the wii. On the PC side, a web browser. Some files on sd card in the /wiibsrv/htdocs folder.
How does it work
Well, nothing magic here, just socket programming. When started, the server initializes the socket subsystem, setups some parameters (bind), and then listens for incoming connections. The Wii's IP is displayed on screen so that clients can connect.
There's two threads, one that waits for buttons, the other that accepts incoming connections and processes them.
It seems the server freezes after two or three requests, especially after loading multiple resources for a single html page. It also drop when requesting a big image. Not time to fix it, sorry :-O
Commented source code is provided. Hope it will help :-) It has been compiled with devkitPro (release 20080602).
This server is rather limited (on purpose).
- process request one after the other (one thread)
- URIs are limited to 1024 chars
- resources are loaded from the front sd card, in the /wiibsrv/htdocs folder
- memory leaks fixing (if any)
- multithread (possibly with pooling), the process_request() function should be ready for that
- error templates stored on sd card, in the /wiibsrv/templates folder
- directory listing
- http headers handling
Once started, you should press the 'A' button to start the accepting thread. Then press 'B' to stop listening. Browse from a web client (use an URL that refers to a file since directory listing is not yet supported).