All examples demonstrate proper way to receive messages:
commit4c6f2084b465ddb3215684e0c0d723ff35ba2645
authorgmallard <allard.guy.m@gmail.com>
Sun, 10 Jul 2016 00:40:34 +0000 (9 20:40 -0400)
committergmallard <allard.guy.m@gmail.com>
Sun, 10 Jul 2016 00:40:34 +0000 (9 20:40 -0400)
tree8546e340b7e2c7bb98c7d9a812fb46eb36b4becd
parentd2a25e51f3ab89851288c919f9e016f1decd19d8
All examples demonstrate proper way to receive messages:

- use select in all cases
- inbound stompngo.MessageData instances can be received from:
-- the subscription specific receive channel
-- the connection level receive channel

Each example shows requirements specific to that example.
In the general case stompngo.MessageData instances could be
received from either source.
ack/ack.go
jinterop/gorecv/gorecv.go
jinterop/gosend/gosend.go
receipts/onack/onack.go
recv_mds/recv_mds.go
srmgor_1conn/srmgor_1conn.go
srmgor_1smrconn/srmgor_1smrconn.go
srmgor_2conn/srmgor_2conn.go
srmgor_manyconn/srmgor_manyconn.go
subscribe/subscribe.go
version.go