[zeromq-dev] identifying a subscriber with xpub xsub

[David Jelenc]

Right. I kind of missed the "how do I identify the client" part. This is 
easier in router-dealer since you can read identity frames.

However, you could still do it with PUB-SUB using manual subscriptions, 
but you'd have use ZAP. I had a similar situation a while ago and I 
identified SUB clients by their public keys.

If you use router-dealer pattern you'll have to manage subscriptions 
manually. Also, you should be aware that router-dealer and pub-sub 
behave differently when queues get full.

Cheers

On 12. 05. 2016 16:52, Pieter Hintjens wrote:
> If you want to do controlled pub-sub, you're better using a
> dealer-router pattern.
>
> On Thu, May 12, 2016 at 4:46 PM, David Jelenc
> <david.jelenc at fri.uni-lj.si> wrote:
>> Sachin,
>>
>> You can use xpub manual subscription. You can read more about it at
>> somdoron's blog:
>>    http://somdoron.com/2014/12/token-pubsub
>>
>> Cheers
>>
>> On 12. 05. 2016 16:40, Sachin Agrawal wrote:
>>>
>>> Hi
>>>
>>> I wanted to know how I can identify a subscriber.
>>>
>>> What I want to do control which topics a client can subscribe to on the
>>> server. I was thinking of using the XPUB/XSUB proxy and then forwarding
>>> only entitled subscription calls to the main publisher. In doing this I
>>> am having a hard time finding where the subscription is coming from.
>>> Does anyone know the ZMQ api that will let me find out who is making the
>>> subscription?
>>>
>>> Regards,
>>>
>>> Sachin
>>>
>>> ------------------------------------------------------------------------
>>> This communication is intended only for the addressee(s), may contain
>>> confidential, privileged or proprietary information, and may be
>>> protected by US and other laws. Your acceptance of this communication
>>> constitutes your agreement to keep confidential all the confidential
>>> information contained in this communication, as well as any information
>>> derived by you from the confidential information contained in this
>>> communication. We do not waive any confidentiality by misdelivery.
>>>
>>> If you receive this communication in error, any use, dissemination,
>>> printing or copying is strictly prohibited; please destroy all
>>> electronic and paper copies and notify the sender immediately. Nothing
>>> in this email is intended to constitute (1) investment or trading advice
>>> or recommendations or any advertisement or (2) a solicitation of an
>>> investment in any jurisdiction in which such a solicitation would be
>>> unlawful.
>>>
>>> Please note that PDT Partners, LLC, including its affiliates, reserves
>>> the right to intercept, archive, monitor and review all communications
>>> to and from its network.
>>>
>>>
>>> _______________________________________________
>>> zeromq-dev mailing list
>>> zeromq-dev at lists.zeromq.org
>>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>>
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>