Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search

[REBOL] Re: tcp ports and buffer size? Holger?

From: petr:krenzelok:trz:cz at: 30-Aug-2001 18:02

----- Original Message ----- From: "Travis Watkins" <[twatkins--datajunction--com]> To: <[rebol-list--rebol--com]> Sent: Thursday, August 30, 2001 4:12 PM Subject: [REBOL] Re: tcp ports and buffer size? Holger?
> I am not a Rebol expert, but I would suspect that it may have > something to do with TCP/IP packet sizes. > > If you receive a packet smaller than your buffer, Rebol sees that > there was not enough data to fill the buffer, and so might assume > that the transfer is complete.
I am not sure and if so, that would be the explanation. But how could I know what packet size opposite side is going to provide me with? :-) Well, I think that if Rebol defined buffer size is larger than packet received, behavior of Rebol depends upon the /no-wait refinement: - if /no-wait is used, rebol simply reads what is available, now matter if you will end-up with an empty string, or some string shorter than defined buffer size. You simply check for 'none, which means end of transmittion. - on the other hand - if /no-wait is not used, and your buffer size is larger than data received, you should end-up with blocking 'copy function behavior, waiting at the port for another data to arrive. But none of above works for me, that's the reason I wonder what is happening ... On the other hand - server on the other side is some strange IBM Rexx stuff, so who knows :-) Thanks for your input anyway ... Cheers, -pekr-