wiki.ziemers.de

ziemer's informatik Wiki

Benutzer-Werkzeuge

Webseiten-Werkzeuge

Zuletzt angesehen: • implemented-product-features
wiki:software:beuthbot:gateway

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen Revision Vorhergehende Überarbeitung
Nächste Überarbeitung 		Vorhergehende Überarbeitung
wiki:software:beuthbot:gateway [13.12.2019 11:25]
Timo Bruns [Functionalities] 		wiki:software:beuthbot:gateway [24.01.2020 15:18] (aktuell)
Tolga Karaoglu [Overview]
Zeile 40: Zeile 40:
  
 [//Appendum:// We decided to establish the server using [[https://nodejs.org/en/|node.js]]. That's why an installation of node and npm is necessary.] [//Appendum:// We decided to establish the server using [[https://nodejs.org/en/|node.js]]. That's why an installation of node and npm is necessary.]
 +
 +
  
 === Telegram Bot === === Telegram Bot ===
Zeile 59: Zeile 61:
 During the implementation of the **gateway** we used [[https://www.sohamkamani.com/blog/2016/09/21/making-a-telegram-bot/|this manual]] as a kind of orientation. During the implementation of the **gateway** we used [[https://www.sohamkamani.com/blog/2016/09/21/making-a-telegram-bot/|this manual]] as a kind of orientation.
  
 +
 +<WRAP pagebreak></WRAP>
 ==== Overview ==== ==== Overview ====
  
Zeile 100: Zeile 104:
 </uml> </uml>
  
 +This class diagram shows the structure around the gateway. Here it is important that there is a StandardizationLayer beforehand, which standsardize the incoming messages. The gateway then directs the message to an NLU service where we get the evaluated object back and compare the scores. The best evaluated message is then forwarded to the registry.
 ==== Functionalities ==== ==== Functionalities ====
  
 === Variables === === Variables ===
 +
 +The defined variables are based on ''express'', ''body-parser'' and ''axios'':
  
 <code javascript> <code javascript>
Zeile 112: Zeile 119:
  
 === API-Call === === API-Call ===
 +
 +Each time our bot is mesaged in the chat, the message will be passed on to the gateway. This is mapped via ''cURL''. All incoming messages use the route ''\message-in''. If the message has no content, the response is empty. The code for the described behaviour looks as follows:
  
 <code javascript> <code javascript>
Zeile 137: Zeile 146:
 === HTTP-POST === === HTTP-POST ===
  
-This section of code shows a request to the Azure service and generates a response which is sent directly to the bot. This is so shaded at this point because Axios asyncron processes the messages and we can be sure that a response has already been received.+This section of code shows a request to the Azure service and generates a response which is sent directly to the bot. The code is shaded like this because Axios processes the messages asyncronous and we have to ensure a response has already been received. The following code snippet shows this more in detail:
  
 <code javascript> <code javascript>
Zeile 161: Zeile 170:
  
 === Server === === Server ===
 +
 +The server is listening on port ''3000'':
  
 <code javascript> <code javascript>
Zeile 191: Zeile 202:
 ==== Versioning ==== ==== Versioning ====
  
-We use [[https://git.ziemers.de/|GitLab]] for versioning.+We use [[https://github.com/|GitHub]] for versioning.
  
 ==== Authors ==== ==== Authors ====
  
-- **Christopher Lehmann** - //Development// & //Documentation//\\+- **Christopher Lehmann** - //Development// & //Documentation// [[https://github.com/Chr1ssy|GitHub]]\\
 \\ \\
-- **Timo Bruns** - //Development//\\ +- **Timo Bruns** - //Development// [[https://github.com/Tarry93|GitHub]] \\\\ 
 +  
 +See also the list of [[https://github.com/beuthbot/gateway/graphs/contributors|contributors]] who participated in this project. 
 +<WRAP pagebreak></WRAP>
wiki/software/beuthbot/gateway.1576232758.txt.gz · Zuletzt geändert: 13.12.2019 11:25 von Timo Bruns

Seiten-Werkzeuge