Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regarding UDP Communication Module #50

Open
BMPC2023 opened this issue Jul 31, 2024 · 1 comment
Open

Regarding UDP Communication Module #50

BMPC2023 opened this issue Jul 31, 2024 · 1 comment

Comments

@BMPC2023
Copy link

Hi Sir @JoelBender ,

I am currently working on BACpypes3. I need the UDPCommunication module for socket communication, which uses the UDPDirector and UDPActor. Please guide me on which classes I need to refer to in BACpypes3.

@JoelBender
Copy link
Owner

Start with the samples in the link layer folder. While UDP is a session-less peer-to-peer protocol, they are named things like "client" and "server" to make it easier to envision things like "initiate a service" and "respond to a request for a service". Note that UDPDirector and UDPActor are terms from "legacy" BACpypes because at the time I thought that both the UDP and TCP portions of a stack should have the same design, not just the same request/indication/response/confirmation API.

Those samples use the lowest kind of PDU, you can of course make your own for your protocol and inherit from the generic Client and Server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants