sockets or tcpclient/udpclient etc..?

[djc]

I am very new to this... I just started playing around with some network
programming. I really only use vb.net. I say that so I don't get the 'use
c/c++' answer. Programming is a hobby for me, not a career. I'm only
interested, at least right now, in playing around with vb.net and maybe some
c#.net. I'm not sure if this is the right
forum or not but...

my first question is to make sure I understand something:
1) the main difference between sockets or the higher level
tcpclient/udpclient etc.. classes is that the latter (derived from the
former) has fewer options/functionality and is synchronous only, for asynch
operation you would need to manage your own threads; AND the former
(sockets) has more options/functionality including their own asynch methods
(beginconnect, endconnect, etc..) which handle the multiple threads for you.

is this correct?

2) If my goal is to eventually right somewhat in depth and/or powerful
network programs should I even bother with the tcpclient/udpclient etc..
classes or should I just start with learning sockets directly?

any input on this would be greatly appreciated. thanks.

 

[cj]

I'm been struggling through sockets recently myself. This link might be
of help.

http://www.catalyst.com/products/socketwrench/tutorial/tcpdoc02.html

 

[djc]

I'll check it out. Thanks.

I'm been struggling through sockets recently myself. This link might be
of help.

http://www.catalyst.com/products/socketwrench/tutorial/tcpdoc02.html