#21 startBristol needs to support distributed operation

closed
Nick Copeland
5
2009-07-22
2009-07-15
Nick Copeland
No

Bristol was always architected to support distribution, engine on one system, GUI on lots of others. The startBristol script however does not allow for this, it either starts the GUI/engine pair together on the same system, or it starts just the GUI and has it connect to the local engine. It needs to be written to support just starting the engine, and the just starting the GUI but catering for the GUI 'host' definition.

Discussion

  • Nick Copeland
    Nick Copeland
    2009-07-16

    • status: open --> pending
     
  • Nick Copeland
    Nick Copeland
    2009-07-16

    This has now been coded and will be in the next distribution, 0.40.5:

    -host - accept a formatted string of <hostname:port>, will support hostname, IP address, ':port' for example. It does not replace the -port option that is actually still used by the engine, this parameter is solely used by the connect() from the GUI.

    -gui - do not invoke the GUI, just the engine, combined with the above option will allow easy distribution of the GUI and engine, have one system use -gui and the GUI systems use '-engine -host enginesystem:5028', etc.

     
  • Nick Copeland
    Nick Copeland
    2009-07-22

    closed.

     
  • Nick Copeland
    Nick Copeland
    2009-07-22

    • status: pending --> closed