another quick question

[iago]

That can replace my code?? Would be a lot easier that way. Does it keep the vbCrlf at the end of each string or throw it away?

Throws it away.

[Camel]

i = InStr(StringData, vbCrLf) 'find position of first vbcrlf

i = instr(1, stringdata, vbcrlf)

[Spht]

i = instr(1, stringdata, vbcrlf)

It does the same thing.

[gotcha_ass]

Dim strLineArray() As String
strLineArray = Split(StringData, vbCrlf)

Now you have a 0-based array containing each line.

Ill just use this then. Thanks Grok

[Yoni]

Code Select Expand

    sck.peekdata ph, 4        'peek at the header up to packet length
    sck.getdata ph, ph.length 'now really get it

Bad!

(That is, assuming PeekData does recv with MSG_PEEK)

[Camel]

gets rid of it

Code Select Expand

Split("1,2,3,4", ",") would return the same thing as

Code Select Expand

Array("1", "2", "3", "4")
and just for refrence, join does the opposite:

Code Select Expand

Join(Array("1", "2", "3", "4"), ",") = "1,2,3,4"

[Camel]

Bad!

(That is, assuming PeekData does recv with MSG_PEEK)

hrm, didnt think about that...i dont think it does, but just to be safe you could do:

Code Select Expand

   sck.getdata ph, 4        'peek at the header up to packet length
    sck.getdata ph.data, ph.length - 4 'grab the data
[edit] comments

[Yoni]

What if you receive under 4 bytes?

[Camel]

What if you receive under 4 bytes?

*kicks yoni*

Code Select Expand

sub fucking_dataarrival(totaldata as intetger)
  if totaldata < 4 then exit sub

[Banana fanna fo fanna]

*kicks yoni*

Code Select Expand

sub fucking_dataarrival(totaldata as intetger)
  if totaldata < 4 then exit sub

Code Select Expand

dim buffer as string
dim plen as integer

sub fucking_dataarival(totaldata as integer)
dim d as string
fucking.getdata d

buffer = buffer & d

if len(buffer) >= 4 and plen = 0 then
'get the length
end if

if len(buffer) >= plen
'houston we have a packet
dim packet as string
packet = left(buffer,plen)
buffer = right(buffer,len(buffer)-len(packet))
plen = 0
end if
end sub


[Yoni]

With Camel's newest code, if you receive between 1 and 3 bytes, they are discarded, causing badly out-of-order packet parsing on the client.

Didn't read through it completely, but Storm's code is probably fine.

[Camel]

With Camel's newest code, if you receive between 1 and 3 bytes, they are discarded, causing badly out-of-order packet parsing on the client.

no they aren't, they stay in the buffer until you read them! i do it all the time!

[Yoni]

Hmm, alright...
What if you receive an entire packet 1 byte at a time?

[dxoigmn]

Code Select Expand

Private Sub Winsock1_DataArrival(ByVal bytesTotal As Long)
bytesTotal is the total number of bytes in the internal buffer.  So even if he does receive 1 byte at a time, then it won't fail.  His code should work fine for BNCS packets.  The only thing I can think of is if he doesn't receive the full BNCS packet content each time.  You would have save the header in a static/global variable and wait until you receive the amount of data the header length says the BNCS packet is.  I believe it is easier to just receive into a buffer, then process packets from that buffer, and not worry about the Winsock's internal buffer.

Edit: added 2 sentences

[Mesiah / haiseM]

ill go with kamakazie on that one, ive never seen a BNCS packet do that, but data frames are spread out in lots of protocols, and i beleive its best to use your own buffer to do the things you want, for obvious reasons already stated.