ó
čEYc@sdef
d
„ƒYZ
dS(tTargetcBsYeZ
dZdddddddd
„Zd„Zd„Zd„Zd„Zd„Z	RS(s%
Identifies the destination of messages.

    A Target encapsulates all the information to identify where a message
    should be sent or what messages a server is listening for.

    Different subsets of the information encapsulated in a Target object is
    relevant to various aspects of the API:

      an RPC Server's target:
        topic and server is required; exchange is optional
      an RPC endpoint's target:
        namespace and version is optional
      an RPC client sending a message:
        topic is required, all other attributes optional
      a Notification Server's target:
        topic is required, exchange is optional; all other attributes ignored
      a Notifier's target:
        topic is required, exchange is optional; all other attributes ignored

    Its attributes are:

    :param exchange: A scope for topics. Leave unspecified to default to the
      control_exchange configuration option.
    :type exchange: str
    :param topic: A name which identifies the set of interfaces exposed by a
      server. Multiple servers may listen on a topic and messages will be
      dispatched to one of the servers selected in a best-effort round-robin
      fashion (unless fanout is ``True``).
    :type topic: str
    :param namespace: Identifies a particular RPC interface (i.e. set of
      methods) exposed by a server. The default interface has no namespace
      identifier and is referred to as the null namespace.
    :type namespace: str
    :param version: RPC interfaces have a major.minor version number associated
      with them. A minor number increment indicates a backwards compatible
      change and an incompatible change is indicated by a major number bump.
      Servers may implement multiple major versions and clients may require
      indicate that their message requires a particular minimum minor version.
    :type version: str
    :param server: RPC Clients can request that a message be directed to a
      specific server, rather than just one of a pool of servers listening on
      the topic.
    :type server: str
    :param fanout: Clients may request that a copy of the message be delivered
      to all servers listening on a topic by setting fanout to ``True``, rather
      than just one of them.
    :type fanout: bool
    :param legacy_namespaces: A server always accepts messages specified via
      the 'namespace' parameter, and may also accept messages defined via
      this parameter. This option should be used to switch namespaces safely
      during rolling upgrades.
    :type legacy_namespaces: list of strings
    cCsP|
|_||_
||_||_||_||_|g
|pEg|_dS(
N(texchangettopict	namespacetversiontservertfanouttaccepted_namespaces(tselfR
RRRRRtlegacy_namespaces((sJ/home/tvault/.virtenv/lib/python2.7/site-packages/oslo_messaging/target.pyt__init__Is	
	
	
	
	
	
c
Ks4x'dD]}|
j|t
||ƒƒ
qWt|
S(NR
RRRRR(sexchangestopics	namespacesversionsserversfanout(t
setdefaulttgetattrR(Rtkwargst
a((sJ/home/tvault/.virtenv/lib/python2.7/site-packages/oslo_messaging/target.pyt__call__Ts




cCst|ƒ
t|
ƒ
kS(
N(
tvars(Rtother((sJ/home/tvault/.virtenv/lib/python2.7/site-packages/oslo_messaging/target.pyt__eq__Zs
cCs||
kS(
N((RR((sJ/home/tvault/.virtenv/lib/python2.7/site-packages/oslo_messaging/target.pyt__ne__]s
c
Cs†g}
xKd
dddddgD]1}t||ƒ}|r|
j
||fƒ

qqWdjg|
D]}d|^qaƒ
}d	|d
S(NR
RRRRRs, s%s=%ss<Target t
>(Rtappendtjoin(RtattrsRt
vt
itvalues((sJ/home/tvault/.virtenv/lib/python2.7/site-packages/oslo_messaging/target.pyt__repr__`s






&
c

Cs
t|ƒ
S(
N(
tid(
R((sJ/home/tvault/.virtenv/lib/python2.7/site-packages/oslo_messaging/target.pyt__hash__js
N(
t__name__t
__module__t__doc__tNoneR
RRRRR(((sJ/home/tvault/.virtenv/lib/python2.7/site-packages/oslo_messaging/target.pyRs6	
	
					
N(tobjectR(((sJ/home/tvault/.virtenv/lib/python2.7/site-packages/oslo_messaging/target.pyt<module>s