Changes between Version 47 and Version 48 of WikiStart


Ignore:
Timestamp:
06/26/19 13:49:22 (5 years ago)
Author:
wouter
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v47 v48  
    11[[PageOutline]]
    22
    3 = Genius2 Parties Server =
     3= GeniusWeb Parties Server =
    44
    5 This is the homepage of the Genius2 parties server.
     5This is the homepage of the GeniusWeb parties server.
    66This server can provide a list of runnable parties, and create running instances of specified parties on a HTPT GET request. When an instance is made, a websocket link to the running party is provided to the caller.
    77
    8 The Genius2 main page is [https://tracinsy.ewi.tudelft.nl/trac/Genius2 here].
     8The GeniusWeb main page is [https://tracinsy.ewi.tudelft.nl/trac/Genius2 here].
    99
    1010
    … …  
    1313== Installation ==
    1414* Install your apache-tomcat 8 installation ​https://tomcat.apache.org/download-80.cgi. You can re-use an existing installation.
    15 * Download the parties server war file from [http://artifactory.ewi.tudelft.nl/artifactory/webapp/#/artifacts/browse/tree/General/libs-release-local/genius2/partiesserver the artifactory]. Go into the latest version of the partiesserver and download (right click) the war file. NOTICE: your browser must have cookies enabled to access the artifactory.
     15* Download the parties server war file from [http://artifactory.ewi.tudelft.nl/artifactory/webapp/#/artifacts/browse/tree/General/libs-release-local/geniusweb/partiesserver the artifactory]. Go into the latest version of the partiesserver and download (right click) the war file. NOTICE: your browser must have cookies enabled to access the artifactory.
    1616* Copy the downloaded war file into the tomcat webapps directory
    1717* (Re)start tomcat
    … …  
    3232This section deals with the communication protocols of the  partiesserver. This is relevant if you need to communicate directly with it, e.g. when you build your own GUI or start up your own parties from a script.
    3333
    34 Other implementations of a partiesserver should adhere to the same communication protocols to ensure compatibility with genius2.
     34Other implementations of a partiesserver should adhere to the same communication protocols to ensure compatibility with GeniusWeb.
    3535
    3636== Context path
    … …  
    4848"required" means that all server implementations should implement this path, and follow the protocol for that path.
    4949
    50 Tech note: on the /run/<party name> requirement, we need this format {{{/run/<party>}}} so that we can extract the context path from a given party reference. This is needed because Genius2 internally passes around only party references. However some services need to access the other services, particularly {{{/free}}}
     50Tech note: on the /run/<party name> requirement, we need this format {{{/run/<party>}}} so that we can extract the context path from a given party reference. This is needed because GeniusWeb internally passes around only party references. However some services need to access the other services, particularly {{{/free}}}
    5151
    5252=== /info
    … …  
    6262A GeneralPartyInfo object contains the following:
    6363{{{
    64         URI                        uri;
    65         genius2.party.Capabilities capabilities;
    66         String                     description;
     64        URI                          uri;
     65        geniusweb.party.Capabilities capabilities;
     66        String                       description;
    6767}}}
    6868
    … …  
    7171A full, updated list is sent over the websocket every time the list changes.
    7272
    73 In the genius2 java implementation these fields are automatically generated from the parties contained in the jar files in the {{{partiesserver/partiesrepo}}} directory that was mentioned above. Other implementations might use a different scheme.
     73In the geniusweb java implementation these fields are automatically generated from the parties contained in the jar files in the {{{partiesserver/partiesrepo}}} directory that was mentioned above. Other implementations might use a different scheme.
    7474
    7575* On the server implementation provided here, the urls look like {{{http://...:8080/partiesserver/run/<party name>}}}
    … …  
    9191
    9292If the connection was succesful and thus the response was a websocket address, the websocket connection implements a {{{Connection<Inform, Action>}}}. This connection has the following protocol:
    93  * it accepts JSON-formatted Inform objects and these are passed into the party (see the the party module in genius2 core)
    94  * can send JSON-formatted Action objects as requested by the agent (see the events module in genius2 core)
     93 * it accepts JSON-formatted Inform objects and these are passed into the party (see the the party module in GeniusWeb core)
     94 * can send JSON-formatted Action objects as requested by the agent (see the events module in GeniusWeb core)
    9595
    9696All parties must be guaranteed to terminate at some time.