acrm
commented
6 years ago Actually the idea was to make it more simply: generator app generate html not by reading some static file and inserting some dynamic info, but by simple Console.WriteLine("<html>...") ; and etc. Also, there is not need to output html to another file, that will be read by Middleware, because we can read in Middleware directly from the processe's OutputStream. Now let'smake it this way, so we will have only one file for each dynamic page: executable generator. This will help us on the next steps.
EkaSe
Our first step to dynamic pages was some generated html, inserted in the content of each html file, that will be requested. It's may be fine for some very general logic, like debugging, but what if we want some more page-specific logic, like greeting an authorized visitor on index page, authorizing visitors on login page and loading saved drawings on canvas page? Dumping all these different logics into single middleware - bad idea. Splitting these logics to several independent middlewares, one per html file - a little bit better, but still has such flaws, as two different files: static html and dynamic middleware for one logical page. The solution might be using pre-build excecutable: just simply a C# console application that output generated html code. For example, when user is requesting an
index.htmlpage, middleware runsindex.exeapplication, catch it's output to stream and returned it as http response.