|
There are lots and lots of ways. Here's one[^].
Now, you need to work out what data you need to send between client and server and then determine a protocol for that data.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
deadlyabbas wrote: How to communicate through the UPD server.
1) Find the electrical outlet that the server is powered from.
2) Unplug the server.
3) Use your saliva to coat your two of your fingers.
4) Stick the fingers from step (3) into the electrical outlet.
5) Return to this forum after completing step (4)
|
|
|
|
|
led mike wrote: 5) Return to this forum after completing step (4)
Or not... 
|
|
|
|
|
shhhhhh, you'll spoil the surprise! 
|
|
|
|
|
You mean, the big fireworks and all the stars and the bright light ? Ooopsss, sorry...
|
|
|
|
|
You're more able in changing identity than writing software, I suppose. 
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
|
1. Client-A listens voice from a computer mic and sends the voice to the server 2. The server relays the voice to Client-B, which outputs the voice to a computer speaker.
3. Both Client-A and Client-B listen and speak.
4. Run in a LAN environment.
|
|
|
|
|
You're really called pandit, aren't you. I might be slow, but that's pretty fscking obvious.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
Stuart Dootson wrote: I might be slow
No, you're not. 
Stuart Dootson wrote: fscking obvious
See that's why I started using frak and fraking, to avoid the asterisks. 
|
|
|
|
|
led mike wrote: See that's why I started using frak and fraking, to avoid the asterisks.
fsck[^] makes much more sense to those with *nix backgrounds.
Best Wishes,
-David Delaune
|
|
|
|
|
Randor wrote: fsck[^] makes much more sense to those with *nix backgrounds.
Ok, if you say so.
Stuart Dootson wrote: I might be slow, but that's pretty fscking file system check obvious.
But, you guys really need to get laid once in a while! 
|
|
|
|
|
Randor wrote: fsck[^] makes much more sense to those with *nix backgrounds.
That's the one...although it's Disk Utilility (OS X) these days rather than fsck!
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
Write a UDP based server and two clients:
1. Client-A listens voice from a computer mic and sends the voice to the server 2. The server relays the voice to Client-B, which outputs the voice to a computer speaker.
3. Both Client-A and Client-B listen and speak.
4. Run in a LAN environment.
|
|
|
|
|
|
Hi!
I am trying to build my own Client Server in UDP.
I have managed to create everything in classes.
The problem is that when all the syntax errors finished, I am getting a link problems for all of the communication functions:
sendto
recvfrom
WSACleanup
closesocket
and more.
I have the library in the project: #include <winsock.h>
The error is:
Error 2 error LNK2019: unresolved external symbol _WSACleanup@0 referenced in function "public: void __thiscall CServer::Handle_Connection(void)" (?Handle_Connection@CServer@@QAEXXZ) CServer.obj
Does anyone knows what is the problem?
Thanks 
<div class="ForumMod">modified on Thursday, April 16, 2009 1:17 PM</div>
|
|
|
|
|
Look at the documentation for WSACleanup, in the section called Requirements you will find a library that is required.
|
|
|
|
|
I have this library.
I looked for other library and I tried it also and same problem.
Error 1 error LNK2019: unresolved external symbol _sendto@24 referenced in function "public: void __thiscall CServer::Handle_Connection(void)" (?Handle_Connection@CServer@@QAEXXZ) CServer.obj Server
Error 2 error LNK2019: unresolved external symbol _WSACleanup@0 referenced in function "public: void __thiscall CServer::Handle_Connection(void)" (?Handle_Connection@CServer@@QAEXXZ) CServer.obj Server
Error 3 error LNK2019: unresolved external symbol _closesocket@4 referenced in function "public: void __thiscall CServer::Handle_Connection(void)" (?Handle_Connection@CServer@@QAEXXZ) CServer.obj Server
all the communication functions????
|
|
|
|
|
ytubis wrote: I have this library.
'Having' it is not enough. Did you add it to the "Additional Dependencies" in your linker settings ?
|
|
|
|
|
This one I do not know how to do?
Can you help me with this?
Where and what do I need to do?
Thanks
|
|
|
|
|
Open your project settings, go to the "Linker" category ->"Input" -> "Additional Dependencies" and there type the name of the required library (which is specified in the documentation).
|
|
|
|
|
This was one of the reasons I was slow to adopt MSVC. Makefiles are very clear, all the information is in one place, and their structure isn't that complex. Beats the hell out of,
"Did you scroll down the menu to the third setting,
pop up the second menu, choose Settings, then click on the color you wanted?"
|
|
|
|
|
That's just a matter of taste. The problem with makefiles is that you have to remember all the commands by heart (or look into a reference). When you have a UI that displays the settings, well, you just have to fill the one you want to. And they are grouped by category which makes things easier.
I much prefer this compared to makefiles.
bulg wrote: "Did you scroll down the menu to the third setting, pop up the second menu, choose Settings, then click on the color you wanted?"
It looks complicated but it's not: the reason is that everything is grouped into categories/sub-categories. What would you prefer: have a loooooong list of 200 entries or having everything grouped in categories ("Linker", "C/C++", ...) ?
|
|
|
|
|
ytubis wrote: and same problem.
Error 1 error LNK2019: unresolved external symbol _sendto@24 referenced in function "public: void __thiscall CServer::Handle_Connection(void)"
No, that's NOT the same problem. It is another link error but now it's a different symbol. If you don't know how to resolve link errors then you need to return to basic C++ studies.
Resolving link errors has nothing to do with Communications Problems, they are C++ beginner issues.
THEREFORE, building a client server system is far beyond the capacity of someone that can't resolve link errors.
|
|
|
|
|
The drop down list will not display any data, I have drop down list sized big and with only a 2 or 4 rows of data. Created a new project and it works there, so must be some setting.
Did trying populating list with:
SendDlgItemMessage(hwndDlg,IDC_COMBO_NDF,LB_ADDSTRING ,(WPARAM)0,(LPARAM)"ZZZ");
But that did not work either and yes with change the properties where owner controled this.
Does anyone have any ideas?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
