Winsock api

[ntaryl]

Hi and Good evening 
Iam here again  and  need some Help
code a client server aplication and i try to use the socket api .
not want  the cSocketclass .
Please small example client server with (connect,close,listen,send.recv  )functions.
thanks for the time 

[Mystical]

uhm, so your asking for source,

well www.pscode.com is your friend in that case.

[brew]

Well, ntaryl, I don't know of any good winsock object tutorials, but you can just use this:

WS.State returns the state of the winsock's current connection. There are 10 possible states:

Code Select Expand


WinSock.State = sckClosed = 0
WinSock.State = sckOpen = 1
WinSock.State = sckListening = 2
WinSock.State = sckConnectionPending = 3
WinSock.State = sckResolvingHost = 4
WinSock.State = sckHostResolved = 5
WinSock.State = sckConnecting = 6
WinSock.State = sckConnected = 7
WinSock.State = sckClosing = 8
WinSock.State = sckError = 9

Self explanitory.

What you want to do to create an outbound tcp connection is....

Code Select Expand


WinSock.Close 'to rid it of any previous connection
WinSock.Connect (STRING) ip address, (INT) porthere

Private Sub WinSock_Connect()
WinSock.SendData "meow mix r00lz" '(in string format)
End Sub

Private Sub WinSock_DataArrival(ByVal bytesTotal As Long)
Dim Data As String
WinSock.GetData Data
MsgBox Data

for a client side connection of some sort.
for a server.... it's like this:

Code Select Expand


Private Sub Form_Load()
WinSock.Close
WinSock.Listen
End Sub

Private Sub Winsock_ConnectionRequest(ByVal RequestID As Long)
Winsock.Close
Winsock.Accept
End Sub...... so on like that


[Hell-Lord]

Code Select Expand

Private Sub Winsock_ConnectionRequest(ByVal RequestID As Long)
Winsock.Close
Winsock.Accept
End Sub...... so on like that

You mean...

Code Select Expand

winsock.Accept RequestID

and

Code Select Expand

Private Sub WinSock_DataArrival(ByVal bytesTotal As Long)
Dim Data As String
WinSock.GetData Data
MsgBox Data


do.....

Code Select Expand

Dim Data as String: Data = Empty

[brew]

Code Select Expand

Private Sub Winsock_ConnectionRequest(ByVal RequestID As Long)
Winsock.Close
Winsock.Accept
End Sub...... so on like that

You mean...

Code Select Expand

winsock.Accept RequestID

and

Code Select Expand

Private Sub WinSock_DataArrival(ByVal bytesTotal As Long)
Dim Data As String
WinSock.GetData Data
MsgBox Data


do.....

Code Select Expand

Dim Data as String: Data = Empty

Oops @ the winsock.accept
But why would I make my "Data = Empty"? That doesn't make sense, in vb6 all variables = 0 or otherwise null until given a set value. I can understand your reasoning if we were using C++....

[l2k-Shadow]

According to the topic, he was asking for winsock API, rather then the VB object. I'd suggest searching for CSocket on google.

[Hell-Lord]

http://www.brutalnet.net/support/index.php?action=tpmod;dl=item26

There is the CSocket

and @Brew i was told to do it that way without much reason but after the data has been set once how would it be cleared.

[Mystical]

maybe cuz he has it as DIM not STATIC?

[Hell-Lord]

O sorry you should use "= VbNullString" .

[brew]

Speaking of vbNullString, what's really better? "" or vbNullString? Ofcourse vbNullString would be the obvious choice, but what about ""? "" is 5 bytes more, but it's faster (I have acually proven this) I made this one quick program where it joins byte arrays with either "" or vbNullString, suprise! 50000 concatinations of "l" with vbNullString took .4655 seconds where "" took acually .001 second less. And there's the third option: Declare a public variable "NulString" or w/e and make it = vbNullString on Form_Load. Good idea? Because the value for vbNullString (it's a constant) would already been picked up and assigned to NulString it would be much quicker then the normal vbNullString, while only taking up maybe 2 more bytes for storage, and maybe 1 per use. (note: I didn't try this but it sounds like a good idea...)

[Barabajagal]

I don't think you're understanding something about vbNullString. It's an empty, null string. "" is not null. That's the difference. Yes, using "" within strings is faster, but when are you ever going to do that normally? you set vbNullString to a string variable to make it null, empty, and void of memory usage.

[brew]

I don't think you're understanding something about vbNullString. It's an empty, null string. "" is not null. That's the difference. Yes, using "" within strings is faster, but when are you ever going to do that normally? you set vbNullString to a string variable to make it null, empty, and void of memory usage.

A null string and empty string are different, for example, an empty string aka "" would take up 6 bytes in total: 4 for the length, and 2 for the null terminators. A nullstring is simply null, taking up zero bytes. Btw: I just realized that setting a variable = to vbNullString is the same as having a null string in the first place, except it doesn't have to keep processing it in the first place, and it doesn't make anything faster. *sigh*

"Yes, using "" within strings is faster, but when are you ever going to do that normally?"
Processor intensive programs?

[Barabajagal]

uhm... a null terminator is one byte... 00.
I asked when you're going to concatenate a string with "". The answer is never.

[MyndFyre]

A null string and empty string are different, for example, an empty string aka "" would take up 6 bytes in total: 4 for the length, and 2 for the null terminators.

I'm relatively certain (though not 100%) that Visual Basic 6 strings are not Unicode.

[Barabajagal]

They can be if you use StrConv on them, but otherwise, no, they're not unicode.