Re: sockets or tcpclient/udpclient etc..?

Tech-Archive recommends: Speed Up your PC by fixing your registry

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

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


djc wrote: 
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.



.

Relevant Pages

  • Re: RMI vs. Sockets vs. ?
    ... RMI is easier than socket programming, ... But sockets can help to connect with application written ... Neglecting for a microsecond the labor cost of creating the apps, by the time you compare the parsing, error-handling and related tasks for a custom message infrastructure against a SOAP-based one with, say Apache and Sun tools, you may find that message sizes are not quite so different, and processing costs closer still. ... Undoubtedly SOAP messages would require more bytes than "equivalent" custom-format compact messages; I'd be dubious of claims that there are significant differences in "speed" once a message reaches its destination. ...
    (comp.lang.java.programmer)
  • Re: C Sockets Newbie: Easy question
    ... If this is an exam question for a sockets course, ... either the file descriptor of the open file (which is a small number ... "Unix Network Programming" by Stevens. ...
    (comp.unix.programmer)
  • Re: Question about CSocket::Receive()
    ... you should not be using synchronous sockets for any purpose. ... It is the nature of TCP/IP that later bytes will not be lost; ... and return the segment up to the terminator; if no terminator was found, ... Receive), etc., but this is all just straightforward programming. ...
    (microsoft.public.vc.mfc)
  • Re: Batch connection to CSKL (was: Trigger CICS transaction from Batch Job)
    ... You can find the fine manual that describes the CICS side of such at z/OS ... in z/OS Communications Server IP Sockets Application Programming Interface ... transaction) that makes managing a listener in CICS quite simple and effective. ... All you need to do is to code the child server transaction in your programming ...
    (bit.listserv.ibm-main)
  • Re: C Sockets Newbie: Easy question
    ... send(fd, outb, strlen(outb), 0) ... and I thought that they ware related with Sockets. ... > either the file descriptor of the open file (which is a small number ... "Unix Network Programming" by Stevens. ...
    (comp.unix.programmer)