Hi
For reference, the demos are in C code (optimised for embedded systems). The web sides are normal html loaded via FTP (rather than being compiled into the code which is typical of many solutions - the advantage being that the web pages can be updated by anyone [eg. customised for a customer] without having to recompile and download via BDM for example. New features can also be added simply by modifying web page content.).
The interface allowing dynamic web page generation and control functions is very simple. In the html file there are a few special markers. Each time the web server encounters one, it asks the application what to do (egs. for a string / value to be displayed, or whether to select a check box or pull down list entry, to disable an element, or to insert a table of length and content to be defined by the application itself).
The application simply starts the web server and passes parameters as to whether it wants it to work with authentication, to support such dynamic features - in which case it must understand the markers so that it knows what to pass back for insertion.
How the web server actually works and how it does the manipulation is not needed to be known by the application - it just supplies the data on request.
One demo is down today due to some work with the board, but when it is back up simply use FTP to its address
ftp://212.254.22.36 and you can see the web pages inside of it and load one to see the control format. You could also modify it and load it back, after which it will appear in the browser next time you update the display.
I am sorry but I don't know whether it will be possible/beneficial to use pearl to program web servers for the NE64 since I don't know enough about it - the NE64 is also very small and what ever is used it should be very efficient. C code is, after all its years, still a very good solution...
The demos are about 25k in code size - with 16 or 32k FLASH file system for the web pages [depending on which demo you are looking at]. The code size value is valid using a good compiler [IAR for example]. The GNU compiler is 'good' but can not match the code size, requiring about 40..60% more space. This can get critical in the NE64, depending on what is to be performed. A good compiler can be very expensive but can also save costs when a larger chip is to be avoided for large production quantities...
Regards