[REBOL] Re: Google + SOAP
From: chris:langreiter at: 30-Apr-2002 15:23
> No, it isn't Rugby's fault, sorry :-) Your scenario is of course
> correct, but replace Rugby and Rebol by Java, etc. - it's just the same.
> If some func takes 10 sec, then it takes 10 sec. Maybe using Java, it
> will be faster, but still blocking.
Petr! NO!!! That's the point! As Java has some wondrous feature set
collectively named "multithreading", you can write non-blocking
servers quite easily ...
> 1) I know where you are trying to point maybe - is that threading? Well,
> you don't need threading to help solve it - you can launch separate task.
Yes, you could write a "broker" which does nothing but shuffle data
from and to "worker" processes, but that won't help you much when the
data transfer process itself is blocking (i.e. when receiving a 10MB
file from a client).
> 5) Rugy is blocking while writing to the port, but even this can be
> solved ...
> 6) Ppl should calm down sometimes :-) Do you want to run server being
> accessed by 10 ppl a sec, so generating 600 request per minute?
There are lots of scenarios where I'd like to use REBOL as an
in-memory data engine and where one web request (e.g.) could easily
result in about 50 queries to that data "server", some of which might
well take some time to complete. So it's absolutely realistic and
there's nothing to "calm down".
> 7) Have you ever tried Rugby? :-)
Yes. Indeed I have written a simple file-sync utility with Rugby (not
unlike Novell's iFolder, but without all the features ;-). It started
to eat up memory after awhile and I never came around to really debug