Problem analysis update

Documents/BT/BT/chap01_existing_technologies.tex

@@ -160,3 +160,7 @@ The feature allows inserting a PHP code between HTML.
 These fragments do not have to form individual independent blocks of code closed in curly brackets.
 The only way how to add user's interaction with the page was web forms before Javascript.
 So most developers should be familiar with this concept.
+
+Files uploading consists of two steps.
+The first step is save the file's information to object representing file. 
+The file is saved as temporary file and the content can be get by standard reading operations.

Documents/BT/BT/chap02_problem_analysis.tex

@@ -1 +1,22 @@
 \chapter{Problem analysis}
+
+The chapter devides the problem of running PHP on the client-side into two parts.
+The first part pays attention to adaptation and changing a PHP paradigm on the client-side.
+The second part describes the integration of Blazor and Peachpie. 
+The advantage of the application's client's part is easy preserving an application state.
+This is achieved by a browser storage, which remains until the application is shutdown.
+The imposibillity of preserving an application state on the server-side causes stateless HTTP protocol. There is an existing way called PHP sessions, but it has some disadvanteges.
+
+The transfer of PHP to the client-side has several problems. 
+The first of them is changing a DOM structure with respect to user's interaction with the page.
+A standard way how to interact is forms.
+The second of them is the server support.
+Superglobals like GET was filled transparently.
+GET variable can be obtained by an URL processing, but POST is a seperate information wrapped in request.
+Another data contained in the request are files.
+
+
+
+
+
+