{#- Connectivity's Trading page (meridian.roles.connectivity.TradingRead), at admin: the key, set or not; the environment, said plainly; each account read-only or with trading enabled, with "Enable trading" for the connectivity role's admin alone (`may_enable`, posting to `enable`); and the placements working, held back or of unknown outcome. Counts and codes only: no account's data. `venue` names the venue; `updates_label` and `updates_none` say how its orders are heard ("Orders read", "Not yet" by default). The vendor's nuance goes at the blocks `vendor_notices` and `vendor_sections`. From 0.32.0 the connection's badge (the agents' demo-only guard, contract v26): Demo where the Environment setting says a demo and the session reached the venue's demo host, Live where neither does, and "Live (environment not confirmed)" where the two disagree; a saved Environment this version refused; and "Sessions", each session's latency (contract v27). -#} {% extends "meridian/base.html" %} {% import "meridian/kit.html" as kit %} {% import "meridian/roles/_rows.html" as om %} {% block content %} {% if notice is defined and notice %}
Connection {% if data.badge == "Demo" %}{{ kit.badge("Demo", "good") }}{% elif data.badge == "Live" %}{{ kit.badge("Live", "warn") }}{% else %}{{ kit.badge(data.badge, "bad") }}{% endif %} The session reached {{ venue|default("the venue") }}'s {{ data.reached_environment }} host; agents may place orders only on a Demo connection.
{% endif %} {% block vendor_notices %}{% endblock %} {% set trading = data %} {% include "meridian/roles/connectivity/_sections.html" %}