Age | Commit message (Collapse) | Author |
|
and a potential client makes sense. Also packing requests and responses into structures / classes is probably a good idea.
|
|
|
|
I'm not really sure I fully like the way I'm designing this, but I guess it could be solved with an HTTP/HTML helper class around the Action class.
However, the HTTP server awfully need reference counting, so it doesn't go away before all of the workers disappear, which means a bit of a redesign of the Listener template.
|
|
fleshed up, and writing the actual server should now be sort of straightforward.
|
|
still needs coding, and won't work as it. And it needs a unit test.
|