Documentation ¶
Index ¶
- func ChangeLog(req *server.Request) (proto.Message, errors.Error)
- func Compile(req *server.Request) (proto.Message, errors.Error)
- func Delete(req *server.Request) (proto.Message, errors.Error)
- func Diff(req *server.Request) (proto.Message, errors.Error)
- func DoCompile(ids []string, path string) (config, hash string, compileErr errors.Error)
- func Explain(req *server.Request) (proto.Message, errors.Error)
- func MultiCompile(req *server.Request) (proto.Message, errors.Error)
- func Read(req *server.Request) (proto.Message, errors.Error)
- func Update(req *server.Request) (proto.Message, errors.Error)
- type NSQEvent
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func Compile ¶
Compile constructs a single, merged, view of config, combining many individual elements
func Diff ¶
Diff will provide a GNU style diff for a configuration at this level in the path with the supplied config (for the given ID).
func DoCompile ¶
DoCompile does the real work for compile - and is implemented like this because we want an HTTP interface in addition to the platform interface
func Explain ¶
Explain will compile config and then explain from which ID the "winning" piece of config came
func MultiCompile ¶
MultiCompile is an equivalent of repeated executions of "Compile". Its goal is to save traffic. The contract of multiconfig is as follows: For every request, compile function is executed. If the received hash is identical to the received hash, empty config will be returned to indicate that no changes were made since the previous config.