
| Current Path : /var/www/web-klick.de/dsh/50_dev2017/1313__procpyjs/src/python/ |
Linux ift1.ift-informatik.de 5.4.0-216-generic #236-Ubuntu SMP Fri Apr 11 19:53:21 UTC 2025 x86_64 |
| Current File : /var/www/web-klick.de/dsh/50_dev2017/1313__procpyjs/src/python/readme.md |
# Readme
## Requirements
###Database:
- Redis
###Python Modules (available in pypi):
- redis
- networkx - *for creating graphs*
- dill - *for storing python objects as strings*
- zerorpc - *for network interfacing*
## 2) Model Description
### the python backend consists of four parts:
- #### processing
- ProcessManager - Interface to the database and most processing-related functions
- ProcessServer & ProcessWorker - Prozesse um die Job Queue zu verwalten und abzuarbeiten
- #### networking
- small script for starting a server interface on a tcp port using zerorpc
- #### base_process
- contains a BaseProcess class which new classes can inherit from to make them compatible with the ProcessManager and get
- #### procpy
- script that can be used as a command line interface to the ProcessManager - *(work in progress)*
## Tests
Tests can be found in the subfolder tests and are a work in progress, but may be helpful to see how different concepts can be implemented.
## TODO
- #### ProcessManager:
- process forking *(should be already possible, but there should be an interface for that)*
- event streams for process reporting while process is running (switching between states, logging) which can be subscribed to and watched on the frontend
- move dumping logic from base_process to database *(process manager should be in control how process is dumped)*
- #### networking:
-
- #### general
- Reading process descriptions from graphml and generate python source code from it
- #### this todo lits