You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.rst
+19-2Lines changed: 19 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,8 @@ The repository provides:
13
13
14
14
+ **dbdatareader** (https://pypi.org/project/dbdatareader/) - Data Reader for .NET `IDataReader <https://docs.microsoft.com/en-us/dotnet/api/system.data.idatareader>`_
15
15
+ **simple-rest-call** (https://pypi.org/project/simple-rest-call/) - wraps `Requests <https://requests.readthedocs.io/>`__ into a simple call
16
+
+ **task-grouping** (https://pypi.org/project/task-grouping/) - organizes a group of tasks with serial/parallel structure,
17
+
carries the arguments for each task unit to run, and assembles all the results into the corresponding tree structure.
16
18
17
19
|
18
20
@@ -81,7 +83,8 @@ Sample PyWebApi Server (for IIS)
81
83
</handlers>
82
84
</system.webServer>
83
85
84
-
.. _script-name:
86
+
.. _script-name:
87
+
85
88
- Modify the ``SCRIPT_NAME`` entry in the <appSettings> section to the Virtual/Application directory (ApplicationPath) you installed in IIS,
86
89
do NOT put a slash ``/`` at the end of the path here. However, if the web app is installed on the root of a website, this entry can be removed.
87
90
@@ -95,7 +98,8 @@ Sample PyWebApi Server (for IIS)
95
98
<addkey="SERVER_DEBUG"value="IIS"/>
96
99
</appSettings>
97
100
98
-
.. _user-script-root:
101
+
.. _user-script-root:
102
+
99
103
- Modify the value of the ``USER_SCRIPT_ROOT`` entry to the container location where all user modules will be organized,
100
104
it is a local file system path which can be an absolute path, or a relative path - relative to the root of the web application
In practice, it's useful to encapsulate multiple related services into a service group and present them externally as a new service
407
+
in order to avoid spreading too much local complexity to the larger scope of the system. In the past we had to write/generate some code or
408
+
at least some scripts for each new service. Let us put aside the development and maintenance costs of these new codes/scripts themselves.
409
+
The new configuration files/tables and the new setup and deployment brought by the new services keep increasing the maintenance complexity of the entire system.
410
+
From the perspective of each individual service, it seems that every configuration item is necessary; but from the perspective of the whole system,
411
+
too many configuration items are repeated in different service nodes. The more redundant configuration, the more messy.
0 commit comments