hello
hello copied to clipboard
travelping
Erlang RPC server framework
Currently hostnames are not mapped to IPs using e.g. `/etc/hosts`. This would be an easy change in the client transport protocol modules. Just from a quick look I would say...
- Update lager and meckfrom hex - Build on travis via rebar3 and mix - Run test on travis via rebar3 and send coverdata We don't run tests and send...
The new lager tracing field `hello_request_peer` can have the following values: - `internal` for internal (pure Erlang) communication when hello services are used - an IP like `127.0.0.1` when HTTP...
When replying asynchronously from a hello server, the server context disappears (due to network failure). For subscriptions to work reliable this mechanism has to become more robust. currently on the...
we need to forward a uuid with hello requests (and log it too) for this purpose structured support from hello would be really nice.
Add documentation about: - services/listeners, binds and routes(which are highly customisable now) - documentation of protocols json over zmtp and ping/pong over zmtp (for developers in other languages)
If no PONG answer to PING, the error should be written and connection should reconnect.
Test, if one machine will be rebooted, and zeromq connection from machine 2 exists, what happens with connection. Test zeromq behaviour before and after fix of #62
This PR adds two options for logging: 1) `logger_formatter`: `json | native` How to print request and response in logs. `json` by default 2) `hidden_params`: `[atom() | binary() | [atom()...
Should be done on security reasons. It should be possible to remove some parts of requests in logs, based on configuration (for example).