VB6 Winsock Control vs. Winsock API
If you are not experienced w/socket based development then I would suggest
going with the control. The API is a lot of work. Have a look at my Winsock
control replacement for an example of what the control might do under the
covers:
http://killervb.com/winsocklib.aspx
"stream-based" programming is enough to worry about without having to worry
about all the other stuff :)
+|+|+|+|+|+|+|+|+|+|+|+|+|+|+|+
Monte Hansen
http://KillerVB.com
+|+|+|+|+|+|+|+|+|+|+|+|+|+|+|+
Quote:
> I've jumped into the winsock pool at the deep end as my first
> application must transfer large quantities of data frequently (up to
> 32K every second).
> What is the practical difference between developing with the Control
> vs. the API? What does the API give you over the Control?
