Changes between Version 510 and Version 511 of WikiStart

Timestamp:

01/30/25 12:16:36 (15 hours ago)

Author:

wouter

Comment:

--

WikiStart

@@ -11 +11 @@
 This page describes the java-based core. This page shows the json structures mostly by example. The details of the core are spelled out by a java-based reference implementation contained here. There is also a python-based core to support python-based programming.
 
-== GeniusWeb overview
+== GeniusWeb servers overview
+You can use the stand-alone runner but for serious negotiations a server-based setup is often more appropriate. The server side modules are in separate projects. This section gives a brief overview of these separate projects. For more details please refer to the wiki pages of those projects.
 
 The web architecture is split into 3 main parts: 
- * a runserver, where an actual negotiation is run. Running a negotiation means execution of the negotiation protocol (as specified in the core) over websockets 
- * a partiesserver, where a party (as specified in the core) can be hooked into a websocket. There are actually 2 types of partiesserver: the "partiesserver" which serves java-based parties, and a pythonpartiesserver which serves python-based parties.
- * a profilesserver, where profiles are served over websockets.
+ * a [https://tracinsy.ewi.tudelft.nl/pubtrac/GeniusWebRunServer runserver], where an actual negotiation is run. Running a negotiation means execution of the negotiation protocol (as specified in the core) over websockets 
+ * a [https://tracinsy.ewi.tudelft.nl/pubtrac/GeniusWebPartiesServer partiesserver], where a party (as specified in the core) can be hooked into a websocket. There are actually 2 types of partiesserver: the "partiesserver" which serves java-based parties, and a pythonpartiesserver which serves python-based parties.
+ * a [https://tracinsy.ewi.tudelft.nl/pubtrac/GeniusWebProfilesServer profilesserver], where profiles are served over websockets.
 
 The services cooperate as in this diagram: