from panda3d.direct import CConnectionRepository
- class CConnectionRepository¶
This class implements the C++ side of the ConnectionRepository object. In particular, it manages the connection to the server once it has been opened (but does not open it directly). It manages reading and writing datagrams on the connection and monitoring for unexpected disconnects as well as handling intentional disconnects.
Certain server messages, like field updates, are handled entirely within the C++ layer, while server messages that are not understood by the C++ layer are returned up to the Python layer for processing.
throw out any msgs that have been queued up for message bundles
- checkDatagram() bool ¶
Returns true if a new datagram is available, false otherwise. If the return value is true, the new datagram may be retrieved via
getDatagram(), or preferably, with
- connectNative(url: panda3d.core.URLSpec) bool ¶
Connects to the server using Panda’s low-level and fast “native net” library.
- considerFlush() bool ¶
Sends the most recently queued data if enough time has elapsed. This only has meaning if set_collect_tcp() has been set to true.
Closes the connection to the server.
- flush() bool ¶
Sends the most recently queued data now. This only has meaning if set_collect_tcp() has been set to true.
- getBdc() panda3d.core.Buffered_DatagramConnection ¶
Buffered_DatagramConnectionobject associated with the repository.
- getCw() panda3d.core.ConnectionWriter ¶
ConnectionWriterobject associated with the repository.
- getDatagram(dg: panda3d.core.Datagram)¶
Fills the datagram object with the datagram most recently retrieved by
- getDatagramIterator(di: panda3d.core.DatagramIterator)¶
DatagramIteratorobject with the iterator for the datagram most recently retrieved by
checkDatagram(). This iterator has already read past the datagram header and the message type, and is positioned at the beginning of data.
- getHandleCUpdates() bool ¶
Returns true if this repository will process distributed updates internally in C++ code, or false if it will return them to Python.
- getMsgChannel(offset: int) int ¶
Returns the channel(s) to which the current message was sent, according to the datagram headers. This information is not available to the client.
- getMsgSender() int ¶
Returns the sender ID of the current message, according to the datagram headers. This information is not available to the client.
- static getOverflowEventName() str ¶
Returns event string that will be thrown if the datagram reader queue overflows.
- getQcm() panda3d.core.QueuedConnectionManager ¶
QueuedConnectionManagerobject associated with the repository.
- getQcr() panda3d.core.QueuedConnectionReader ¶
QueuedConnectionReaderobject associated with the repository.
- getSimulatedDisconnect() bool ¶
Returns the simulated disconnect flag. While this is true, no datagrams will be retrieved from or sent to the server. The idea is to simulate a temporary network outage.
- getStream() panda3d.core.SocketStream ¶
SocketStreamthat internally represents the already-established HTTP connection. Returns NULL if there is no current HTTP connection.
- getVerbose() bool ¶
Returns the current setting of the verbose flag. When true, this describes every message going back and forth on the wire.
- hasOwnerView() bool ¶
Returns true if this repository can have ‘owner’ views of distributed objects.
- isBundlingMessages() bool ¶
Returns true if repository is queueing outgoing messages into a message bundle
- isConnected() bool ¶
Returns true if the connection to the gameserver is established and still good, false if we are not connected. A false value means either (a) we never successfully connected, (b) we explicitly called
disconnect(), or (c) we were connected, but the connection was spontaneously lost.
- sendDatagram(dg: panda3d.core.Datagram) bool ¶
Queues the indicated datagram for sending to the server. It may not get sent immediately if collect_tcp is in effect; call
flush()to guarantee it is sent now.
- sendMessageBundle(channel: int, sender_channel: int)¶
Send network messages queued up since
- setClientDatagram(client_datagram: bool)¶
Sets the client_datagram flag. If this is true, incoming datagrams are not expected to be prefixed with the server routing information like message sender, channel number, etc.; otherwise, these server fields are parsed and removed from each incoming datagram.
- setConnectionHttp(channel: panda3d.core.HTTPChannel)¶
Once a connection has been established via the HTTP interface, gets the connection and uses it. The supplied
HTTPChannelobject must have a connection available via get_connection().
- setHandleCUpdates(handle_c_updates: bool)¶
Set true to specify this repository should process distributed updates internally in C++ code, or false if it should return them to Python.
- setHandleDatagramsInternally(handle_datagrams_internally: bool)¶
Sets the handle_datagrams_internally flag. When true, certain message types can be handled by the C++ code in in this module. When false, all datagrams, regardless of message type, are passed up to Python for processing.
The CMU distributed-object implementation requires this to be set false.
- setPythonRepository(python_repository: object)¶
Records the pointer to the Python class that derives from
CConnectionRepository. This allows the C++ implementation to directly manipulation some python structures on the repository.
- setSimulatedDisconnect(simulated_disconnect: bool)¶
Sets the simulated disconnect flag. While this is true, no datagrams will be retrieved from or sent to the server. The idea is to simulate a temporary network outage.
- setTcpHeaderSize(tcp_header_size: int)¶
Sets the header size of TCP packets. At the present, legal values for this are 0, 2, or 4; this specifies the number of bytes to use encode the datagram length at the start of each TCP datagram. Sender and receiver must independently agree on this.
- setTimeWarning(time_warning: float)¶
Directly sets the time_warning field. When non zero, this describes every message going back and forth on the wire when the msg handling time is over it
- setVerbose(verbose: bool)¶
Directly sets the verbose flag. When true, this describes every message going back and forth on the wire.
May be called at application shutdown to ensure all threads are cleaned up.
Send a set of messages to the state server that will be processed atomically. For instance, you can do a combined setLocation/setPos and prevent race conditions where clients briefly get the setLocation but not the setPos, because the state server hasn’t processed the setPos yet
Toggles the current setting of the verbose flag. When true, this describes every message going back and forth on the wire.