Changes between Version 256 and Version 257 of WikiStart

Timestamp:

09/24/19 11:38:07 (5 years ago)

Author:

wouter

Comment:

--

WikiStart

@@ -336 +336 @@
 
 
-
+=== NegoSettings
+We discuss two common NegoSettings in more detail, with some examples. 
+
+
+Typically the session settings looks like this:
+{{{
+{"SAOPSettings": {
+    "participants":[
+        {"party":"http://party1","profile":"ws://profile1"},
+        {"party":"http://party2","profile":"ws://profile2"}],
+    "deadline":{"deadlinetime":{"millis":100}}
+}}
+}}}
+
+The "SAOPSettings" indicates that these settings are SAOPSettings and (see Settings.getProtocol) will be interpreted by the SAOP protocol.
+
+The participants is a list with PartyWithProfile items: a "party" field containing a http address on a partiesserver, and a "profile" field containing a websocket address on a profilesserver.
+
+The deadline contains the deadline for the SAOP, which is how long the negotiation can last.
+
+For different protocols, the contents will differ.
+
+For a tournament, the NegoSettings typically look like this:
+{{{
+{"AllPermutationsSettings":{
+ "parties":["http://server/../party1","http://server/../party2"],
+ "profiles":["ws://server/../profile1","ws://server/../profile2","ws://server/../profile3"],
+ "reuseParties":false,
+ "partiesPerSession":2,
+ "sessionsettings":{"SAOPSettings":{"participants":[],"deadline":{"deadlinetime":{"millis":10}}}}}}
+}}}
+
+
+The parties is a list of party URIs, just like in the session settings 
+
+The profiles is a list of profile URIs, just like in the session settings
+
+If reuseParties is set to to false, parties are drawn from the list without return. If it is set to true, parties are drawn with return (meaning all parties can occur multiple times in each session)
+
+partiesPerSession sets the number of parties (and matching profiles) for each session. Profiles are always drawn without return (never appear twice in a session)
+
+sessionsettings contains basically all the normal run-sessionsettings. This is used as a "template" for all sessions of the tournament. You can put any use any session setting here, and each session will be run according to the protocol you select here. In the example we use the SAOP protocol which takes participants and deadline as arguments, as discussed above. The participants list this time is empty, the AllPermutationsProtocol adds the the required parties to this list. So if you provide a non-empty list here, then these parties would be present in every session in the tournament.
 
 = Writing a party in Java