networking stuff..

How efficient is REBOL at networking? (Fairly general statement eh?) We've developed an application in C++ that creates a number of worker threads and simply listens on a TCP/IP port for incoming messages, quite often the load is quite intense (the application is infrastructure management software) as agents are trying to connect with the server to send their details through (only 557 bytes at a time per agent); at the moment the application we've made performs quite well. However, I can see REBOL being a perfect replacement for our agents and our server, provided that it would be able to handle the load. I'm VERY new to REBOL but so far I'm very impressed (anything by Carl must be good; I'm an Amiga freak from way back). Does it have any concept of threads? Or does it just magically handle the network connections without me having to worry about it? Cheers, -Matt

Matt, You may want to check out Rugby which utilizes non-blocking I/O instead of threads (which Rebol doesn't have). Rugby is a broker for Rebol. Depending on your application logic it handles a lot of concurrent connections. www.rebolforces.com/~erebol --Maarten

Yeah, I've just finished reading about that - might have a look at some samples and see how I go! If I can phase out the C++ code and make everything REBOL it would make the application so much easier to implement would make modifications relatively easy for the end user (at the moment I'm the sole developer and am constantly adding new features for the users). Regards, -Matt