qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-827) Client binding for the "go" programming language.
Date Fri, 10 Apr 2015 19:53:12 GMT

    [ https://issues.apache.org/jira/browse/PROTON-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14490252#comment-14490252

ASF subversion and git services commented on PROTON-827:

Commit d6f1b8371d0dca82531b363f2a2ebdee55e56dfa in qpid-proton's branch refs/heads/master
from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=d6f1b83 ]

PROTON-827: Initial work on Go language client for proton.

This is the beginning of a Go language client for proton. There are 2 Go modules, with
rudimentary documentation;

qpid.apache.org/proton: AMQP/Go data type mapping, message encoding/decoding.
qpid.apache.org/proton/event: Go proton event API, pump proton event loop from Go connections.

examples/go/event/broker.go is a simple broker-like example, ported from examples/python/broker.py.
You can use examples/python/simple_send.py and simple_recv.py to see it in action.

examples/go/exampe.go is a very incomplete, speculative idea about the future Go-friendly
user API.

The event API is not intended to be the final user API, it is a foundation for developing
that API in Go.

See proton-c/bindings/go/README.md for more.

> Client binding for the "go" programming language.
> -------------------------------------------------
>                 Key: PROTON-827
>                 URL: https://issues.apache.org/jira/browse/PROTON-827
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: proton-c
>    Affects Versions: 0.9
>            Reporter: Alan Conway
>            Assignee: Alan Conway
> Develop a reactive API binding in "go" <http://golang.org/>, similar to the existing
reactive python API illustrated in examples/python. It should follow the pattern of the existing
python and C reactive APIs as far as possible while respecting common conventions and idioms
of the go langauge.

This message was sent by Atlassian JIRA

View raw message