----- Original Message ----- From: "Maarten Koopmans" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 10, 2001 11:16 PM Subject: [REBOL] Fw: Re: about the benchmarks
> The OS helps you here: it accepts a connection even when the application is > busy. This called the backlog. It is set to 5 by default. So you can have 5 > times the number of Rugby servers in terms of connections before blocking > starts. > > You can change this value in hipe-serv.r It was 15 (commented out for Mac > compat). You can comment it in, build-rugby.r and you are done. Higher than > 15 most of the time is useless (see the OS docs for details). Heh, that's cool. I didn't know what is that item good for in port structure. One question: getting stubs to client get's there func's source code along with regby refinements (/http ...), but what if my function calls another custom one, or even worse, some dll routine? You could get routine transferred to client, but hardly whole library ... just curious ... ... maybe you could add one to three sentences comment to each module to your website. It would help ppl to understand, what is inside imo .... -pekr- > > --maarten > > > > > > > Thanks a lot, that's what I what I wanted to know. I also thought about > > push > > > (in opposite to deffered polling) IRC like behavior, but the question > is, > > if > > > it is really good to keep "channels" opened, as it will surely mean > memory > > > allocations.... > > > > > > In regards to scenario you describe below - you can have several Rugby > > > servers running. The basic load balancing is - you simply loop your > > requests > > > thru all your running Rugby server instances. My question is - what > > happens > > > if you are trying to connect to Rugby server, and it is bussy doing some > > > task? You will block, till connection is not accepted or refused, right? > > So, > > > it is good to write server tasks in some clever way, perform some part > of > > > the task, and return back to main loop to see if someone wants to > connect > > to > > > us (and queue the request).Wasn't such concept present back in Rebol 1.0 > > > days, called continuations? > > > > > > Or maybe you don't need to solve such situation, as the whole stuff is > > > pretty fast? Well, I tried rather complex db queries and I can handle 3 > > > requests per second, what is more - odbc connection is blocking, so > untill > > > you get your query result back, you simply wait. > > > > > > It will be even easier, if 3.0 introduces more i/o granularity and > ability > > > to influence connection/disconnection phases, so maybe it will be > possible > > > to wait some 0.1 sec for connection, and if Rugby server would be busy, > > > discard it, and try to connect to another one. > > > > > > Anyway, - thanks for your description. btw: are you working on any > > improved > > > docs? It would be great to see Rugby mentioned on RT's website. What is > > > planned for next Rugby release? > > > > > > Thanks, > > > -pekr- > > > > > > > > -- > To unsubscribe from this list, please send an email to > [EMAIL PROTECTED] with "unsubscribe" in the > subject, without the quotes. -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
