Documentation
¶
Index ¶
Constants ¶
This section is empty.
Variables ¶
View Source
var ErrSsh = fmt.Errorf("ssh error")
View Source
var SECURE_KEY = securecookie.GenerateRandomKey(32)
Functions ¶
Types ¶
type Client ¶
type Client struct {
// contains filtered or unexported fields
}
wrapper for websocket, should we make generic?
type Rpc ¶
type Rpc struct { Method string `json:"method,omitempty"` Id int64 `json:"id,omitempty"` Params json.RawMessage `json:"params,omitempty"` }
type RpcReply ¶
type RpcReply struct { Id int64 `json:"id,omitempty"` Result json.RawMessage `json:"result,omitempty"` Error string `json:"error,omitempty"` }
type SecretCookie ¶
type SecretCookie = string
type Server ¶
type Server interface { Subscribe(topic string, browser Peer) Drop(topic string, browser Peer) Publish(topic string, data []byte, more []byte) }
can configuration be a standard topic then? do we publish to it to set it? channels can have different behaviors for newcomers: get summary, get all, get new. Most common would be get summary. maybe each topic should be a file in a directory (separate? what if we are running from readonly? readonly starter config?) there are also more complex behaviors like update by character then commit.
type WebChannel ¶
type WebChannel struct {
// contains filtered or unexported fields
}
more generally this may be a pub sub channel with a default of all
Click to show internal directories.
Click to hide internal directories.