By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,777 Members | 1,311 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,777 IT Pros & Developers. It's quick & easy.

Opinion Needed: Information transfer over TCP

P: 9
I was curious if anyone could give me their opinion what would be the most stable way to transfer information from Server to client... here are my examples of what I would like to do...

Currently I have a MultiClient TCPServer/Client I use for chat in my main Application, this is handled with simple text transfer, this opens one socket per connection.

Now I would like to send other Application information along these same lines, and I was wondering if I should modify the current connection to handle, for example, an XML file, that would be parsed and executed by Client using the same Writeln/Readln operations, or if I should open another socket using a different type of Protocol to send the "file" or "object" with the new information.

I eventually will be sending such files as images and zip and data files too.

I know it can be done both ways, but before I commit to either option I was hoping for some input. I am learning mostly as I go, and I am fairly new to VB.NET using 2005.
Sep 11 '07 #1
Share this question for a faster answer!
Share on Google+

Post your reply

Sign in to post your reply or Sign up for a free account.