Simple Question About Sending/Receiving Data To/From A Server
-
Good people, I built an application that needs to send information to and receive it from a server. I have one questions, how do I do that? :laugh: I am new to this aspect of programming. Thanks for any information you can provide. Blitz
-
Good people, I built an application that needs to send information to and receive it from a server. I have one questions, how do I do that? :laugh: I am new to this aspect of programming. Thanks for any information you can provide. Blitz
There are several methods you could use - WCF, sockets, HTTP... What are your requirements? What kind of data?
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
There are several methods you could use - WCF, sockets, HTTP... What are your requirements? What kind of data?
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001Thanks for your reply. I need to send at least 2 and up to 7 separate strings. In essence, the user will be sending some authentication data to the server which will consists of an authentication code and some other identifying information (e.g. a MAC Address, user ID, etc...). This will enable me to uniquely identify the user in the database on the server. Then, once the server has certified that the user is unique or doesn't exist, then it will send back an authorization which will either be, I suppose, true or false, etc... Thanks again.
-
Thanks for your reply. I need to send at least 2 and up to 7 separate strings. In essence, the user will be sending some authentication data to the server which will consists of an authentication code and some other identifying information (e.g. a MAC Address, user ID, etc...). This will enable me to uniquely identify the user in the database on the server. Then, once the server has certified that the user is unique or doesn't exist, then it will send back an authorization which will either be, I suppose, true or false, etc... Thanks again.
If the server is a web server, you could use a web service to do that. If the user has an account on the server, he could just use the built-in .Net authentication stuff. If the server does not meet any of those criteria, I'd use sockets.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
