Re: [twsocket] Need example code foridentifyingarecordbeforeprocessing

2006-11-21 Thread Clay Shannon
Oh, never mind, I see it in your other answer now (I'm reading answers
posted over the weekend and this mailing list (live) simultaneously),
namely:

MyOpCode := PInteger(@Buffer)^;

Thanks, Francois!

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Clay Shannon
Sent: Monday, November 20, 2006 10:04 AM
To: 'ICS support mailing'
Subject: Re: [twsocket] Need example code
foridentifyingarecordbeforeprocessing

 Right. But since you send integer data type, you WILL have #126 in the
binary data !

In the infamous words of Kip Dynamite, Dang it

Is there any LineEnd value I can set that will be safe to assume it won't
get sent in integer data?

Or will I need to pull out the OpCode any time a record comes in, without
knowing which type of record it is until I read the OpCode?

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Francois Piette
Sent: Monday, November 20, 2006 9:59 AM
To: ICS support mailing
Subject: Re: [twsocket] Need example code for
identifyingarecordbeforeprocessing

  OnDataAvailable() should only fire once for each record, because I am
  having
  the sender add a #126 (~) as the last byte of each record, and using
  LineMode with LineEnd = #126.

 WARNING: Since your record contains binary data, it could contains a #126
as

 part of the data. So the line mode will not work as you expect !

 But only if a tilde (#126) is included in the binary data sent, right?

Right. But since you send integer data type, you WILL have #126 in the
binary data !

Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
Author of ICS (Internet Component Suite, freeware)
Author of MidWare (Multi-tier framework, freeware)
http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  If the reader of this message is not the intended recipient,
you are hereby notified that your access is unauthorized, and any review,
dissemination, distribution or copying of this message including any
attachments is strictly prohibited.   If you are not the intended
recipient, please contact the sender and delete the material from any
computer.
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Re: [twsocket] Need example code foridentifyingarecordbeforeprocessing

2006-11-21 Thread Francois PIETTE
  Right. But since you send integer data type, you WILL have #126 in the
 binary data !

 In the infamous words of Kip Dynamite, Dang it

 Is there any LineEnd value I can set that will be safe to assume it won't
 get sent in integer data?

Defenitely none !

 Or will I need to pull out the OpCode any time a record comes in, without
 knowing which type of record it is until I read the OpCode?

You can.
Or you can follow my recommandation about escaping delimiter. This is very 
common practice with binary data.
Or send your data in ascii.
Did you miss my previous reply where I was talking about binary data and 
excape mechanism ?

--
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
http://www.overbyte.be


-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be