Network Communication
-
I'm a newbie at programming. I need to build an Client/Server application in which my home computer is likely to be the server but possibly the school server. At most there will be no more than 200 clients of which only a few will be accessing the server at anyone time. I've heard lots about XML and ASP.Net but know nothing about them. Does VB.Net have a simple thing to use like C++'s Winsock?? What would be suitable approach use for the network communcation side of this. oh yea, the data will be being transferred over the internet to the users home systems. Cheers Thanks in advance Jace
-
I'm a newbie at programming. I need to build an Client/Server application in which my home computer is likely to be the server but possibly the school server. At most there will be no more than 200 clients of which only a few will be accessing the server at anyone time. I've heard lots about XML and ASP.Net but know nothing about them. Does VB.Net have a simple thing to use like C++'s Winsock?? What would be suitable approach use for the network communcation side of this. oh yea, the data will be being transferred over the internet to the users home systems. Cheers Thanks in advance Jace
Without knowing much about this I suggest you look at the System.Net namespace. You can use FileWebRequest and FileWebResponse to send files back and forth. There are tons of docs on these features.
-
I'm a newbie at programming. I need to build an Client/Server application in which my home computer is likely to be the server but possibly the school server. At most there will be no more than 200 clients of which only a few will be accessing the server at anyone time. I've heard lots about XML and ASP.Net but know nothing about them. Does VB.Net have a simple thing to use like C++'s Winsock?? What would be suitable approach use for the network communcation side of this. oh yea, the data will be being transferred over the internet to the users home systems. Cheers Thanks in advance Jace
What is the expected use case for someone interacting with the system? Is it a scenario in which a client is supposed to transfer file(s) from client to server, or is the user interacting with a user interface, entering information into a database? Is it going to be deployed as a browser-based application or as a rich-client application? It all depends really on the function of the system and how people will use it.
-
I'm a newbie at programming. I need to build an Client/Server application in which my home computer is likely to be the server but possibly the school server. At most there will be no more than 200 clients of which only a few will be accessing the server at anyone time. I've heard lots about XML and ASP.Net but know nothing about them. Does VB.Net have a simple thing to use like C++'s Winsock?? What would be suitable approach use for the network communcation side of this. oh yea, the data will be being transferred over the internet to the users home systems. Cheers Thanks in advance Jace
xtremean wrote (via email): i...need to be able send text strings, .jpg and .bmp file types OK, so this might not be the simplest solution for a "newbie".... that being said, here's what I would imagine doing if I were writing a custom application to do this kind of thing: On the client side you'll have some kind of form, possibly attached to a
NotifyIcon
(for ease of use, like an IM client) that allows the user to select a file (or files). Using theFile
andFileStream
you open up the client file, establish aNetworkStream
connection to the server usingTcpClient
andTcpListener
and useNetworkStream
andFileStream
on the server side to read the stream and write it to a file. The server is going to listen on several ports for several incoming connections, each connection aTcpListener
running on its own thread, so there would be the need to start each on its own, using Asynchronous callbacks and theIAsyncResult
interface. At a network level, if it is over the Internet, you might consider a establishing a VPN connection between the client location and the server location, which should protect and encrypt the transfers and prevent having to write code dealing with that aspect of things. Then again, you could establish an FTP site somewhere and get WS_FTP Pro, or something, and enable people to upload to the FTP site. This can even use SSL for encryption, protecting the confidentiality of the information being passed.