Re: Bob Nash socket client

Correct - I was hoping someone else might have tackled the incorrect size
issue, but failing that, I will plunge in - in fact I have already
started... will keep everyone posted.

- Roger

At 07:34 AM 3/3/2003 -0800, you wrote:
>Bob's Client/Server relies on a fixed header size to differentiate
>between the header and data. I'm guessing it was the server which
>crashed (you didn't say). The FNAME buffer (defined in the
>CONNECTINFO class in Resources.F) size is 28 bytes.
>
>Regarding header validation, you'll need to add some other
>verification mechanism. Its quite possible that the header and body
>of the message arrive together on the server. The only way to
>separate them with the existing scheme is by length - the first 20 are
>the header.
>
>Mike
>
>-----Original Message-----
>From: sftalk-bounce_at_forth.com [mailto:sftalk-bounce_at_forth.com]On
>Behalf
>Of Roger Dube
>Sent: Monday, March 03, 2003 6:02 AM
>To: sftalk_at_forth.com
>Subject: [sftalk] Bob Nash socket client
>
>
>Bob and folks, I have been toying with the socket client that Bob
>posted.
>The client currently sends a 20 byte header to the server... all is
>well if
>that header is the correct length, but if I change the length of the
>header
>to, say, 30 bytes, I get access violations - I would like to simply
>disconnect any requests that do not have the right header length
>without
>affecting anyone else that might be connected... before I dig in, has
>anyone else looked at this?
>
>Thanks!
>
>----------------------------------------------------------------------
>Dr. Roger Dube
>
>rdube_at_entropylock.com
>
>President/CEO
>Digital Authentication Technologies, Inc.
>
>http://www.entropylock.com
>
>TEL +1.561.392.7404
>
>PO Box 811564
>Boca Raton, FL 33481-1564
>
>----------------------------------------------------------------------
>
>This E-mail message and any attachments have been scanned for viruses
>and
>are believed to be free of any virus or other defect that might affect
>any
>computer system into which it is received and opened. However, it is
>the
>responsibility of the recipient to ensure that it is virus free and no
>responsibility is accepted by Digital Authentication Technologies,
>Inc. for
>any loss or damage arising in any way from its use.
>
>This email message is for the sole use of the intended recipient(s)
>and may
>contain confidential and privileged information. Any unauthorized
>review,
>use, disclosure or distribution is prohibited. If you are not the
>intended
>recipient, please contact the sender by reply email and destroy all
>copies
>of the original message. Any views expressed in this message are those
>of
>the individual sender, except where the sender specifically states
>them to
>be the views of Digital Authentication Technologies, Inc.
>
>----------------------------------------------------------------------
>sftalk_at_forth.com The SwiftForth programming discussion email list
>To unsubscribe, send subject "unsubscribe" to sftalk-request_at_forth.com
>For list command help, send subject "help" to sftalk-request_at_forth.com
>Message archives are located at http://www.forth.com/archive/sftalk
>----------------------------------------------------------------------
>This list is a forum for SwiftForth users. For product support and
>bug
>reports, please send email to support_at_forth.com
>----------------------------------------------------------------------
>
>
>----------------------------------------------------------------------
>sftalk_at_forth.com The SwiftForth programming discussion email list
>To unsubscribe, send subject "unsubscribe" to sftalk-request_at_forth.com
>For list command help, send subject "help" to sftalk-request_at_forth.com
>Message archives are located at http://www.forth.com/archive/sftalk
>----------------------------------------------------------------------
>This list is a forum for SwiftForth users. For product support and bug
>reports, please send email to support_at_forth.com
>----------------------------------------------------------------------

----------------------------------------------------------------------
Dr. Roger Dube

rdube_at_entropylock.com

President/CEO
Digital Authentication Technologies, Inc.

http://www.entropylock.com

TEL +1.561.392.7404

PO Box 811564
Boca Raton, FL 33481-1564

----------------------------------------------------------------------

This E-mail message and any attachments have been scanned for viruses and
are believed to be free of any virus or other defect that might affect any
computer system into which it is received and opened. However, it is the
responsibility of the recipient to ensure that it is virus free and no
responsibility is accepted by Digital Authentication Technologies, Inc. for
any loss or damage arising in any way from its use.

This email message is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. Any unauthorized review,
use, disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and destroy all copies
of the original message. Any views expressed in this message are those of
the individual sender, except where the sender specifically states them to
be the views of Digital Authentication Technologies, Inc.

----------------------------------------------------------------------
sftalk_at_forth.com The SwiftForth programming discussion email list
To unsubscribe, send subject "unsubscribe" to sftalk-request_at_forth.com
For list command help, send subject "help" to sftalk-request_at_forth.com
Message archives are located at http://www.forth.com/archive/sftalk
----------------------------------------------------------------------
This list is a forum for SwiftForth users. For product support and bug
reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Mon Mar 03 2003 - 07:47:45 PST