altid / client Goto Github PK

As things are currently, everything works alright, but there should be some place for discussion about where to put things as languages are added.

Leaving this open to facilitate.

Currently, altid-cli is designed to only attach to a single service at a time. In order to facilitate connecting to more during startup/runtime, a few options are available.

1. A scan command, /scan would look for mDNS entries for _altid.tcp. Adding a service would then be by name, such as /service add irc, and that would use the mDNS data to get the ultimate ip:port tuple to use.
2. Directly dealing, /service add irc 192.168.0.4:564
3. Configuration mapping, a config file would hold the name-to-ip mappings, and you'd call it by name. /service add irc

Of the three, each has its merits. There will be mDNS entries up and running for any given service, and it is the least overhead; but the other options offer the potential to dial remote services as well.

My initial taste is for both 1 and 2; if an IP is explicitly stated, use it; else use an mDNS entry lookup.

@altid/architecture

Currently, altid-cli is meant for single-service connections. Related to #1, we want to be able to cleanly connect and interact.

• Should be user friendly
• Should be fault tolerant to services closing

To achieve this, the first approach I have is to add a /service command, as discussed in #1. /service add foo /service rm bar.
Additionally on startup, a list of requested local/remote services could be iterated, such as altid-cli irc discord sms.

@altid/architecture

to make it simple to write clients, this allows you to do things like as follows:

cmds, _ := client.GetCommands()
mytype.cmdlist = cmds

for _, cmd := range cmds {
    if cmd.Name == somecmd {
        client.Send(cmd, somedata)
    }
}

return errors.New("Command not supported")

@altid/devs
And that would comprise all command wrangling, aside from client-specific commands.