Local connection is UDP first, then TCP? #75
Closed
ColtonIdle
started this conversation in
General
Replies: 2 comments
-
|
Yes that's how it works. The device can only be found via udp broadcast, specifically. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Nice. I'm actually way more familiar with tcp so that's good to know. At first I thought it was all udp. Cheers
Sent from Proton Mail Android
…-------- Original Message --------
On 4/28/24 10:03 AM, parnic wrote:
Yes that's how it works. The device can only be found via udp broadcast, specifically.
—
Reply to this email directly, [view it on GitHub](#75 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AHSHXZO66J326EIWNPGXD5TY7T6RJAVCNFSM6AAAAABG4WWR5WVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TENJSGM2TC).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Just wanting to make sure that I understand how this library works. I'm only interested in a local connection which is done over udp . But it seems like once the service is found via udp 255.255.255.255 1444 then you get an ip + port... which you can then use tcp to connect to?
Or do i have something backwards here? Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions