Archived

This topic is now archived and is closed to further replies.

TeraZen

I don't believe it!

Recommended Posts

TeraZen    122
I don''t believe it! I''ve started to program VB long ago... With Vb 3.0 & 4.0 Mswinsck.ocx (The Microsoft Winsock Control that comes with VB) was not able to handle more than one socket... Now you just need to duplicate the control to have a multi-user server! But... what about the efficiency? Is the interface of that control fast enough to make such a server? Or should I use winsock.dll (a lot of work, for those who knows: api pogramming)... Thanks TeraZen

Share this post


Link to post
Share on other sites
barazor    122
winsock api is not really all that hard, just make some kind of little wrapper(a .cls file maybe) that does all the dirty work, shouldnt be too complicated

Share this post


Link to post
Share on other sites
ajoling    202
IMO, the only drawback of using the OCX is that it
1) Requires the Winsock control (*.ocx)
2) It takes more memory to use it than using the API.

I made a Winsock API VB webserver, you can download the source on planetsourcecode.com It''s pretty unique, I haven''t seen one with downloadable source yet somewhere else..

Share this post


Link to post
Share on other sites