Well, here's my take. I want to set up (say) a Rugby server, which will accept client connections and process them. I'd like each connection to be handled in its own thread (let's keep it simple and leave thread pools, resource utilization and the like out of this) as I need each client's response to be in reasonable time (pretend the processing involves I/O or something). I'm kinda astonished that I can't do this in Rebol proper. Unless I'm missing something real obvious, the only way that I can do this is to rely on code that implements a cooperative multitasking queue (a la Rugby) or roll my own (!).
One way out of is to rely on cgi-bin as the multi-threaded server, but then every client invocation causes a new Rebol process to be launched, which is resource intensive (perhaps there is a way to jigger the apache.conf file to keep one or more processes running, but that's beyond me). I hate to bring in language wars (as I am quite taken with Rebol, and have been able to do some really cool stuff with this) but a multi-threaded server like this is bread 'n butter in Java (and others). Just my $0.02 (ie. I'm not trying to incite a flame war). parki... > > IIRC Carl has strong feelings against multi-threading. It can be a > powerful tool, yes, but do we *need* it, and is it worth the > complexity that comes with it? > > -- Gregg > > -- > To unsubscribe from this list, just send an email to > [EMAIL PROTECTED] with unsubscribe as the subject. > > -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
