On Thu, Sep 26, 2013 at 2:55 PM, Asko Soukka <notifications@github.com>wrote:

> In collective/pdfpeek/zamqp/utils.py:
>
> > @@ -0,0 +1,78 @@
> > +# -*- coding: utf-8 -*-
> > +from collective.pdfpeek.interfaces import IPDFDataExtractor
> > +from collective.pdfpeek import interfaces
> > +from collective.pdfpeek.conversion import remove_image_previews
> > +from collective.zamqp.interfaces import IProducer
> > +from collective.zamqp.consumer import Consumer
> > +from collective.zamqp.producer import Producer
> > +from plone.app.uuid.utils import uuidToObject
> > +from plone.registry.interfaces import IRegistry
> > +from plone.uuid.interfaces import IUUID
> > +from zope.component import getUtility
> > +from zope.interface import Interface
> > +
> > +QUEUE_NAME = "collective.pdfpeek.queue"
>
> Should this product support scenarios where it is used in multiple
> Plone-sites in the same Zope-server?
>
 yes it should



> Or multiple Plone-sites (each on the different server) using the same
> broker?
>

hmm what is the overhead in using a different broker for each zope?

> The latter would require queue to be defined in buildout (e.g. with
> product configuration or environment variable).
>


> The former would require magical ${site_id} in consumer to register queues
> with a site name in them, and calculated routing key in producers to do the
> same.
>



-- 
Best Regards,

Christian Ledermann

Nairobi - Kenya
Mobile : +254 702978914

<*)))>{

If you save the living environment, the biodiversity that we have left,
you will also automatically save the physical environment, too. But If
you only save the physical environment, you will ultimately lose both.

1) Don’t drive species to extinction

2) Don’t destroy a habitat that species rely on.

3) Don’t change the climate in ways that will result in the above.

}<(((*>