summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorkali kaneko (leap communications) <kali@leap.se>2020-06-04 12:10:07 +0200
committerkali kaneko (leap communications) <kali@leap.se>2020-06-12 20:02:51 +0200
commit5b0f50abe5718d83cdc62623faad854f810df640 (patch)
tree42b8fe4bae55e48e7702301a52d7befb6269cb5a
parent139588ea81c8d6e62a2830c1522fe4dc5a074c24 (diff)
[refactor] add comment, unsure about using this
Signed-off-by: kali kaneko (leap communications) <kali@leap.se>
-rw-r--r--gui/backend.go8
1 files changed, 8 insertions, 0 deletions
diff --git a/gui/backend.go b/gui/backend.go
index 885ece2..812258d 100644
--- a/gui/backend.go
+++ b/gui/backend.go
@@ -122,6 +122,12 @@ func (s status) fromString(st string) status {
}
}
+// FIXME -----------------------------------------------------------------------
+// at some moment I thought this was a good idea, but probably is overkill -
+// and not used right now. Discuss with meskio in code review, and very likely
+// remove it - there are probably better ways of dealing with tracking of user
+// actions more towards the ui layer.
+
// An action is originated in the UI. These represent requests coming from the
// frontend via the C code. VPN code needs to watch them and fullfill their
// requests as soon as possible.
@@ -144,6 +150,8 @@ func (a actions) MarshalJSON() ([]byte, error) {
return b.Bytes(), nil
}
+// -----------------------------------------------------------------------------
+
// The connectionCtx keeps the global state that is passed around to C-land. It
// also serves as the primary way of passing requests from the frontend to the
// Go-core, by letting the UI write some of these variables and processing