You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw how to start the first node and join nodes using an hmac.
I saw how to use the cli to create/run mkproc using an hmac on the command line.
On Windows, using mkproc is not evident due to multi-line nature of description of process to run.
As the only resort, we need to create an app that uses the go-circuit client api. That said the client api itself does not seem to expose the hmac capability. That capability seems to be exposed in a lower-level code-gangsta api. My question is do you expect others to use the code-gangsta directly or should the go-circuit api not expose the hmac capability and avoid using the codegangsta stuff directly?
The text was updated successfully, but these errors were encountered:
On 22 February 2016 at 11:12, David Marceau [email protected]
wrote:
I saw how to start the first node and join nodes using an hmac.
I saw how to use the cli to create/run mkproc using an hmac on the command
line.
On Windows, using mkproc is not evident due to multi-line nature of
description of process to run.
As the only resort, we need to create an app that uses the go-circuit
client api. That said the client api itself does not seem to expose the
hmac capability. That capability seems to be exposed in a lower-level
code-gangsta api. My question is do you expect others to use the
code-gangsta directly or should the go-circuit api not expose the hmac
capability and avoid using the codegangsta stuff directly?
—
Reply to this email directly or view it on GitHub #25.
I saw how to start the first node and join nodes using an hmac.
I saw how to use the cli to create/run mkproc using an hmac on the command line.
On Windows, using mkproc is not evident due to multi-line nature of description of process to run.
As the only resort, we need to create an app that uses the go-circuit client api. That said the client api itself does not seem to expose the hmac capability. That capability seems to be exposed in a lower-level code-gangsta api. My question is do you expect others to use the code-gangsta directly or should the go-circuit api not expose the hmac capability and avoid using the codegangsta stuff directly?
The text was updated successfully, but these errors were encountered: