Hi all, I have had some discussions about adding persistent connections to Rugby. It may be good to know that I tested this feature for 4.3 but that on an Ethernet the setup time for /no-wait/direct TCP ports is so short that reusing connections is actually fourt times slower. I have no clue why!
SOme other news: Rebol seems to be inconsistent in its network behaviour. I tested on Linux 2.4.x libc6, but Petr runs on 2.2.16 and observes CPU eating. Shouldn't the same script run the same on all platforms? Under NT 4 I managed to eat up all CPU if I didn't read alkl bytes on a server before closing a port. This is fixed in 4.3 My (wild) guess: Rebol puts a small wrapper on TCP/IP stacks in different OS'es with more and more advanced features, such as non-blocking I/O. As some platforms/kernels have (different) bugs you see this in Rebol scripts.... --Maarten -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
