I don't believe it!

Started by
1 comment, last by TeraZen 22 years, 3 months ago
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
Last of the Returners
Advertisement
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
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..
www.persistentrealities.com for Inline ASM for VB, VB Fibre, and other nice code samples in C++, PHP, ASP, etc.<br/>Play Yet Another Laser Game!<br/>

This topic is closed to new replies.

Advertisement