&GR2@s9ddlZddlZddlZddlZddlZddlmZmZmZddlm Z m Z m Z dZ dZ dZdZdZdZd d d d d gZdZdZdZdZdZdZdZdZGdddeZGdddeZGdddeZGdddeZ dS)N) basestringbytesstr)Property getErrorMsgUIDg?closedclosingZwaitingZhostingZ connectedzClosed on command.zUnspecified problemz/Invalid stop reason specified (must be string).zConnection timed out.zHandshake timed out.zHandshake failed.z2Handshake failed (context cannot connect to self).zClosed from other end.c@s"eZdZdZddZdS)ConnectionCollectionz ContextConnectionCollection() A list class that allows indexing using the name of the required Connection instance. cCsot|tr[|s$tdnxD|D]}|j|kr+|Sq+Wtd|ntj||SdS)Nz#An empty string is not a valid key.z!No connection know by the name %s) isinstancerKeyErrornamelist __getitem__)selfkeycrK/Applications/pyzo2014a/lib/python3.4/site-packages/iep/yoton/connection.pyr1s z ConnectionCollection.__getitem__N)__name__ __module__ __qualname____doc__rrrrrr)s rc@seZdZdZdddZeddZeddZed d Zed d Z ed dZ eddZ eddZ eddZ eddZeddZeddZeddZeddZedd Zed!d"Zd#d$d%Zd&d'd(Zd&d)d*Zd+d,Zd-d.Zd/d0Zd1d2Zd3d4Zd5d6Zd7d8Zd9d:Z d&S); Connectionad Connection(context, name='') Abstract base class for a connection between two Context objects. This base class defines the full interface; subclasses only need to implement a few private methods. The connection classes are intended as a simple interface for the user, for example to query port number, and be notified of timeouts and closing of the connection. All connection instances are intended for one-time use. To make a new connection, instantiate a new Connection object. After instantiation, either _bind() or _connect() should be called. cCs||_||_d|_d|_d|_d|_d|_d|_t|_ t j |_ t j |_ tj|_|jddS)Nrr)_context_name _hostname1 _hostname2_port1_port2_id2_pid2 TIMEOUT_MIN_timeoutyotonSignal_timedout_signal_closed_signal threadingRLock_lock _set_status)rcontextrrrr__init__Ps         zConnection.__init__cCs|jS)zG Get the hostname corresponding to this end of the connection. )r!)rrrr hostname1tszConnection.hostname1cCs|jS)zj Get the hostname for the other end of this connection. Is empty string if not connected. )r")rrrr hostname2{szConnection.hostname2cCs|jS)z Get the port number corresponding to this end of the connection. When binding, use this port to connect the other context. )r#)rrrrport1szConnection.port1cCs|jS)zf Get the port number for the other end of the connection. Is zero when not connected. )r$)rrrrport2szConnection.port2cCs |jjS)z? The id of the context on this side of the connection. )rZ_id)rrrrid1szConnection.id1cCs|jS)zD The id of the context on the other side of the connection. )r%)rrrrid2szConnection.id2cCs tjS)z\ The pid of the context on this side of the connection. (hint: os.getpid()) )osgetpid)rrrrpid1szConnection.pid1cCs|jS)zE The pid of the context on the other side of the connection. )r&)rrrrpid2szConnection.pid2c Cs3|jjz|jdkSWd|jjXdS)z Get whether this connection instance is alive (i.e. either waiting or connected, and not in the process of closing). r N)r/acquire_statusrelease)rrrris_alives zConnection.is_alivec Cs3|jjz|jdkSWd|jjXdS)z< Get whether this connection instance is connected. r N)r/r=r>r?)rrrr is_connecteds zConnection.is_connectedc Cs3|jjz|jdkSWd|jjXdS)z Get whether this connection instance is waiting for a connection. This is the state after using bind() and before another context connects to it. r N)r/r=r>r?)rrrr is_waitings zConnection.is_waitingcCs|jS)z Signal emitted when the connection closes. The first argument is the ContextConnection instance, the second argument is the reason for the disconnection (as a string). )r,)rrrrr szConnection.closedcCsdd}dd}tS)z Set/get the amount of seconds that no data is received from the other side after which the timedout signal is emitted. cSs|jS)N)r()rrrrfgetsz Connection.timeout..fgetcSsPt|ttfs$tdn|tkrCtdtn||_dS)Nztimeout must be a number.ztimeout must be at least %1.2f.)rintfloat ValueErrorr'r()rvaluerrrfsets  z Connection.timeout..fset)locals)rCrHrrrtimeouts  zConnection.timeoutcCs|jS)a This signal is emitted when no data has been received for over 'timeout' seconds. This can mean that the connection is unstable, or that the other end is running extension code. Handlers are called with two arguments: the ContextConnection instance, and a boolean. The latter is True when the connection times out, and False when data is received again. )r+)rrrrtimedouts zConnection.timedoutcCsdd}dd}tS)ad Set/get the name that this connection is known by. This name can be used to obtain the instance using the Context.connections property. The name can be used in networks in which each context has a particular role, to easier distinguish between the different connections. Other than that, the name has no function. cSs|jS)N)r )rrrrrCszConnection.name..fgetcSs+t|tstdn||_dS)Nzname must be a string.)rrrFr )rrGrrrrHszConnection.name..fset)rI)rCrHrrrrs  zConnection.nameg@cCs |j|S)z flush(timeout=3.0) Wait until all pending packages are send. An error is raised when the timeout passes while doing so. )_flush)rrJrrrflushszConnection.flushNcCs>|dkrt}n|jttgkr.dS|j|dS)aJ close(reason=None) Close the connection, disconnecting the two contexts and stopping all trafic. If the connection was waiting for a connection, it stops waiting. Optionally, a reason for closing can be specified. A closed connection cannot be reused. NT)STOP_DEFAULT_REASONr> STATUS_CLOSEDSTATUS_CLOSING_general_close_method)rreasonrrrcloses  zConnection.closecCsX|dkrt}n|jtkr(dS|jtkrH|jtdS|j|dS)a close_on_problem(reason=None) Disconnect the connection, stopping all trafic. If it was waiting for a connection, we stop waiting. Optionally, a reason for stopping can be specified. This is highly recommended in case the connection is closed due to a problem. In contrast to the normal close() method, this method does not try to notify the other end of the closing. NF)STOP_UNSPECIFIED_PROBLEMr>rOrPr0rQ)rrRrrrclose_on_problem0s   zConnection.close_on_problemcCs|j}|jtt|ts.t}n|rJ|jrJ|jn|jt|j j |||j j rt |}td||fndS)zJ general close method used by both close() and close_on_problem() zYoton: %s connection closed: %sN)r>r0rPrrSTOP_INVALID_REASONrA_notify_other_end_of_closingrOr emitr_verbose STATUSMAPprint)rrRZsend_stop_messageZ old_statustmprrrrQRs       z Connection._general_close_methodcCs tdS)N)NotImplemented)rhostnameportZ max_triesrrr_binduszConnection._bindcCs tdS)N)r])rr^r_rJrrr_connectxszConnection._connectcCs tdS)N)r])rrJrrrrL{szConnection._flushcCs tdS)N)r])rrrrrW~sz'Connection._notify_other_end_of_closingcCs tdS)N)r])rpackagerrr _send_packageszConnection._send_packagecCs tdS)N)r])rrbrrr_inject_packageszConnection._inject_packagec Csq|jjzO||_|dkr[|jjr[t|}td||j|jfnWd|jj XdS)zj Used to change the status. Subclasses can reimplement this to get the desired behavior. rzYoton: %s at %s:%s.N) r/r=r>rrYrZr[r!r#r?)rstatusactionrrrr0s   $zConnection._set_status)!rrrrr2propertyr3r4r5r6r7r8r;r<r@rArBr rrJrKrrMrSrUrQr`rarLrWrcrdr0rrrrr?s8 $      " #      rc@seZdZdZdS)InterConnectiona InterConnection(context, hostname, port, name='') Not implemented. Communication between two processes on the same machine can also be implemented via a memory mapped file or a pype. Would there be an advantage over the TcpConnection? N)rrrrrrrrrhs rhc@seZdZdZdS) UDPConnectiona UDPConnection(context, hostname, port, name='') Not implemented. Communication can also be done over UDP, but need protocol on top of UDP to make the connection robust. Is there a reason to implement this if we have Tcp? N)rrrrrrrrris ri)!r9systimer-r) yoton.miscrrrrrrr'rOrPZSTATUS_WAITINGZSTATUS_HOSTINGZSTATUS_CONNECTEDrZrNrTrVZ STOP_TIMEOUTZSTOP_HANDSHAKE_TIMEOUTZSTOP_HANDSHAKE_FAILEDZSTOP_HANDSHAKE_SELFZSTOP_CLOSED_FROM_THERErrobjectrrhrirrrrs4     ^