if i'm correct UDP is when you use peer to peer architecture...in my case i'll use a client/server architecture so i think TCP is great in this case no?
i'll check this codec (Opus Codec)
Opus is a lossy audio coding format developed by Xiph and standardized by the IETF, designed to efficiently code speech and general audio in a single format, while remaining low-latency enough for real-time interactive communication and low-complexity enough for low end ARM3 processors
Anyway Thank you mate
if i'm correct UDP is when you use peer to peer architecture...in my case i'll use a client/server architecture so i think TCP is great in this case no?
No, that's not the case. UDP is just a connectionless, unreliable protocol, so you can send a single packet to a destination IP address/port and you don't need to be connected to it, and you won't know if it gets there using UDP by itself. TCP is a connection oriented streaming protocol, so it requires 2 IP addresses to connect, and the data sent is streamed and guaranteed to get there in the order sent.
Both TCP and UDP can be used with peer-to-peer, and both can be used for client/server. Typically a game will include both TCP (for sending those must have data pieces ), and UDP (for sending the often updated states of players).
In your case, since you're doing interactive audio, you might want to use UDP since it will decrease communication time to/from others. If you happen to drop a packet myou'll get a blip in the audio, but the other guy can just say, "What was that?"
My Gamedev Journal: 2D Game Making, the Easy Way
---(Old Blog, still has good info): 2dGameMaking
-----
"No one ever posts on that message board; it's too crowded." - Yoga Berra (sorta)
if i'm correct UDP is when you use peer to peer architecture
if i'm correct UDP is when you use peer to peer architecture
No. Client/Server vs Peer-to-peer is a topology; TCP vs UDP is a protocol.
That's a pretty basic networking fundamental, so my guess is you're not particuarly well versed in how to run a networking-based business.
What value are you adding to your customers by starting this business, that existing solutions like Webex or Google Hangouts or Skype or Zoom don't already give them (for cheap or free)?
I know the TCP and UDP are two different protocol
Client/Server Clients are connected via server and a direct connection between users is not allowed...Client/Server is safe for users and you know why...
I'm a Network programmer and not business manager i'll ask my team about your question if they know how to run a business or not lol
Free or payed it's not my work...my work is to write some code in a company called NadTalk
if i'm correct UDP is when you use peer to peer architecture...in my case i'll use a client/server architecture so i think TCP is great in this case no?
No, that's not the case. UDP is just a connectionless, unreliable protocol, so you can send a single packet to a destination IP address/port and you don't need to be connected to it, and you won't know if it gets there using UDP by itself. TCP is a connection oriented streaming protocol, so it requires 2 IP addresses to connect, and the data sent is streamed and guaranteed to get there in the order sent.
Both TCP and UDP can be used with peer-to-peer, and both can be used for client/server. Typically a game will include both TCP (for sending those must have data pieces ), and UDP (for sending the often updated states of players).
In your case, since you're doing interactive audio, you might want to use UDP since it will decrease communication time to/from others. If you happen to drop a packet myou'll get a blip in the audio, but the other guy can just say, "What was that?"
