One way to extend the Straw user interface would be to have an internal web server. This would let us work around ../HtmlWidget limitations (image cache for MozEmbed and WebKit) and even provide Straw features as a web service to remote Straw processes and web browsers.
Three degrees to choose from:
- Local filesystem: simple. disk access slow. no forms or other dynamic features.
- HTTP server: more complex. anything a web interface can do.
- HTTP proxy: tweak how all of web looks.