Currently I use different instances to do the processing, with a manager that justs
handles redirecting connections. My manager still bogs at 8 connections--but I am
counting on increasing performance. Under the right circumstances you might try
busting up your processes so they contain break points--allowing you to stop, process
other stuff, then continue where you left off. You possibly might be able to use
'do/next for this.
--Ryan
[EMAIL PROTECTED] wrote:
> Hi,
>
> I am trying to write a simple rebol based server.
>
> I have one problem though: How do I handle a very high load of say, 50 concurrent
>users continuously.
>
> If more than 5 users try to connect before accepting, the backlog is full, but if a
>task is sufficiently complex then I can't call a 'wait [port 0]' often enough.
>
> A problem that may be solved once async I/O is full available (I have tinkered a bit
>with async clients, but I can't get servers to work).
>
> Any ideas?
>
> Thanks,
>
> Maarten Koopmans
>
> --
> To unsubscribe from this list, please send an email to
> [EMAIL PROTECTED] with "unsubscribe" in the
> subject, without the quotes.
--
Ryan Cole
Programmer Analyst
www.iesco-dms.com
707-468-5400
"I am enough of an artist to draw freely upon my imagination.
Imagination is more important than knowledge. Knowledge is
limited. Imagination encircles the world." -Einstein
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
