commit a08d6a592bd026273ce435590c2f94ce6b242792
parent 1e83b73ea47b295f031edf6a95834db8df7996c2
Author: Joel-Haeberli <haebu@rubigen.ch>
Date: Sun, 26 May 2024 16:12:05 +0200
docs: enhancements
Diffstat:
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/docs/content/results/discussion.tex b/docs/content/results/discussion.tex
@@ -1,11 +1,19 @@
\section{Discussion}
What is the significance of your results? – the final major section of text in the paper. The Discussion commonly features a summary of the results that were obtained in the study, describes how those results address the topic under investigation and/or the issues that the research was designed to address, and may expand upon the implications of those findings. Limitations and directions for future research are also commonly addressed.
+Our work shows that withdrawals in GNU Taler are possible using the payment service provider Wallee. The C2EC implementation shows how the process can be implemented and integrated into the rest of the Taler ecosystem.
+The design of the Terminals API was a major field of work during the process. Only after a few iterations, the specification was ready. The iterations were necessary to sharpen the understanding of how the terminal and C2EC must interact and integrate with the existing Taler components in order to make the withdrawals functional.
+
+The implementation of the existing Bank-Integration and Wire-Gateway API were a challenge because they must be implemented with great care to not violate the specification. Another challenging task was the design of C2EC. To create a useful, robust and extensible design, other components of Taler must have been understood. This task was a little more time consuming than initially planned.
+
+A challenge which was encountered during the implementation of the terminal application and the C2EC component, was the concurrency of processes. To make the withdrawal flow as easy and useful as possible to the user, a lot of tasks need to be covered in the background and run in parallel. This added the technical requirement to decouple steps and leverage retries to increase the robustness of the process.
+
+During the integration phase towards the end of the implementation it became obvious that a simple authorization was not enough to imitate the real time feeling of the withdrawal. Other Requests were necessary to do so. To findout which requests needed to be filed against the Wallee backend needed to be investigated. The documentation does explain which states exists in Wallee's transaction scheme but it does not explain, which operation do trigger the transition of one state to another.
\section{Future Work}
-As stated in the discussion the implementation of the framework does suffer from some architectural short comings. Also other parts must be further improved. Additionally to such clean up duties, the system can be extended. To give myself and others interested to collaborate some ideas what can be done, I provide a list of future work. The list might not be complete and any new idea is appreciated. I split the future work into two parts. The second list, is a list of ideas how the existing logic can be extended to make the system easier to use or to add new functionality. The second list contains technical debts which I tried to keep low but due to the lack of time could not prevent.
+As stated in the discussion the implementation of the framework does suffer from some architectural short comings. Also other parts must be further improved. Additionally to such clean up duties, the system can be extended. To give myself and others interested to collaborate some ideas what can be done, I provide a list of future work. The list might not be complete and any new idea is appreciated. I split the future work into two parts. The second list, is a list of ideas how the existing logic can be extended to make the system easier to use or to add new functionality. The second list contains technical debts.
\subsection{Extensions}
\begin{enumerate}
diff --git a/docs/thesis.pdf b/docs/thesis.pdf
Binary files differ.
