You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This library provides the user with the ability to automatically deploy and manager proxy processes for handling
8
+
network communication with remote devices using various protocols. A proxy to each remote peer is established in
9
+
a separate process from the managing application. A manager class handles socket communication between the proxy
10
+
subprocess and its owner. Individual protocols are implemented as plugins to this library. Integration with
11
+
event and asyncio event loops are supported for each of the proxy and manager processes.
12
+
13
+
14
+
## Automatically installed dependencies
15
+
- python = ">=3.10,<4.0"
16
+
17
+
[//]: #(# Documentation)
18
+
19
+
[//]: #(More detailed documentation can be found on [ReadTheDocs](https://eclipse-volttron.readthedocs.io/en/latest/external-docs/lib-protocol-proxy/index.html. The RST source)
20
+
21
+
[//]: #(of the documentation for this component is located in the "docs" directory of this repository.)
22
+
23
+
# Installation
24
+
This library can be installed using pip:
25
+
26
+
```shell
27
+
pip install lib-protocol-proxy
28
+
```
29
+
30
+
Protocol Proxy plugins should include "protocol-proxy" as a requirement, so users of existing
31
+
plugins are encouraged to instead install the plugin for that pacakge directly.
32
+
33
+
# Development
34
+
This library is maintained by the VOLTTRON Development Team.
35
+
36
+
Please see the following [guidelines](https://github.com/eclipse-volttron/volttron-core/blob/develop/CONTRIBUTING.md)
37
+
for contributing to this and/or other VOLTTRON repositories.
38
+
39
+
[//]: #(Please see the following helpful guide about [using the Protocol Proxy](https://github.com/eclipse-volttron/lib-protocol-proxy/blob/develop/developing_with_protocol_proxy.md))
40
+
41
+
[//]: #(in your VOLTTRON agent or other applications.)
42
+
43
+
# Disclaimer Notice
44
+
45
+
This material was prepared as an account of work sponsored by an agency of the
46
+
United States Government. Neither the United States Government nor the United
47
+
States Department of Energy, nor Battelle, nor any of their employees, nor any
48
+
jurisdiction or organization that has cooperated in the development of these
49
+
materials, makes any warranty, express or implied, or assumes any legal
50
+
liability or responsibility for the accuracy, completeness, or usefulness or any
51
+
information, apparatus, product, software, or process disclosed, or represents
52
+
that its use would not infringe privately owned rights.
53
+
54
+
Reference herein to any specific commercial product, process, or service by
55
+
trade name, trademark, manufacturer, or otherwise does not necessarily
56
+
constitute or imply its endorsement, recommendation, or favoring by the United
57
+
States Government or any agency thereof, or Battelle Memorial Institute. The
58
+
views and opinions of authors expressed herein do not necessarily state or
59
+
reflect those of the United States Government or any agency thereof.
_log.warning(f'Outbound socket to {s.getpeername()} was ready, but no outbound message was found.')
266
+
try:
267
+
peer_name=f'to {s.getpeername()}'
268
+
exceptOSError:
269
+
peer_name=''
270
+
# TODO: Why is this getting triggered (apparently on every send)? _log.warning(f'Outbound socket to {peer_name} was ready, but no outbound message was found.')
0 commit comments