merlimat commented on a change in pull request #1764: WIP - Pulsar Go client library URL: https://github.com/apache/incubator-pulsar/pull/1764#discussion_r187534072
########## File path: pulsar-client-go/examples/consumer-listener/consumer-listener.go ########## @@ -0,0 +1,55 @@ +// +// Licensed to the Apache Software Foundation (ASF) under one +// or more contributor license agreements. See the NOTICE file +// distributed with this work for additional information +// regarding copyright ownership. The ASF licenses this file +// to you under the Apache License, Version 2.0 (the +// "License"); you may not use this file except in compliance +// with the License. You may obtain a copy of the License at +// +// http://www.apache.org/licenses/LICENSE-2.0 +// +// Unless required by applicable law or agreed to in writing, +// software distributed under the License is distributed on an +// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +// KIND, either express or implied. See the License for the +// specific language governing permissions and limitations +// under the License. +// + +package main + +import ( + "../../pulsar" + "fmt" + "log" +) + +func main() { + client := pulsar.NewClient(). + ServiceUrl("pulsar://localhost:6650").Build() + + channel := make(chan pulsar.ConsumerMessage) + + consumer, err := client.NewConsumer(). + Topic("my-topic"). + SubscriptionName("my-subscription"). + SubscriptionType(pulsar.Shared). + MessageListener(channel). + Subscribe() + if err != nil { + log.Fatal(err) + } + + // Receive messages from channel + for cm := range channel { + consumer := cm.Consumer Review comment: In this case we don't care about the consumer, because the message can only come from that same consumer. However, it might be possible to use a single channel to receive messages from multiple consumers. That's the reason the channel contains a `ConsumerMessage` struct rather than a plain `Message` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
