[1/3] from: koopmans::itr::ing::nl at: 13-Aug-2001 14:54
This one is for Pekr ;-) A general load-balancing scheme would be: 1) Create a rugby server that is the load balancer. 2) All servers register there 3) clients register/unregister there and ask for a server such as: rexec [ add-client me] serv: rexec [ get-server] rexec/with [ my-func ] serv I currently use rugby client from a FastCGI app to a dedicated rugby server, nothing fancy there in terms of load balancing. We rununder Linux / Solaris with MySQL and Oracle links, no problems there. Your ODBC crash may result from state you keep overthe requests? Unsetting al request based words may help to prevent this. I have had a similar problem when I accidentally created self-modifying code, resulting in a crash in stead of unpredictable behaviour. BTW: Rugby 4 (Rugby 4 U) is almost finished with automated stub generation and oneway and deferred sexec and finally! documentation
[2/3] from: petr:krenzelok:trz:cz at: 13-Aug-2001 20:08
----- Original Message ----- From: "Maarten Koopmans" <[koopmans--itr--ing--nl]> To: <[rebol-list--rebol--com]> Sent: Monday, August 13, 2001 2:54 PM Subject: [REBOL] rugby load-balancing
> This one is for Pekr ;-) > A general load-balancing scheme would be:
<<quoted lines omitted: 6>>> rexec/with [ my-func ] serv > I currently use rugby client from a FastCGI app to a dedicated rugby
> nothing fancy there in terms of load balancing. We rununder Linux /
> with MySQL and Oracle links, no problems there.
So, if I understand it correctly, your Apache/FastCGI script (assuming you use FastCGIExternalServer set-up) connects to Rebol listening process (open fastcgi://, not multiplexed, just default as presented by RT), which is simply client to your main Rebol Rubgy server?
> Your ODBC crash may result from state you keep overthe requests?
I think not. I never seen it under Linux though. I get the error on local machine, under Apach Win2K set-up - there's tcp problems somewhere, if you press reload in IE imediatelly after Rebol process started to do some stuff ...
> Unsetting al > request based words may help to prevent this. I have had a similar problem > when I accidentally created self-modifying code, resulting in a crash in > stead of unpredictable behaviour. > > BTW: Rugby 4 (Rugby 4 U) is almost finished with automated stub generation > and oneway and deferred sexec and finally! documentation
eh, I may be dumb, but what is "stub"? :-) Thanks, -pekr-
[3/3] from: m:koopmans2:chello:nl at: 13-Aug-2001 20:35
Hey Pekr, FastCGI: we use cgi compatibility mode (option 2 from the docs) and let apache do the work there. Gives pretty good perormance as it instantiates multiple and keeps them alive. I have the solution for a standalone FastCGI to Rugby mentally worked out, but I have little time for that ;-( A stub is a (set of) client side substitute(s) for remote functions. You'll be able to do something like: database-logic: import-from/as-context tcp://cool.com:8001 which will make wrapper functions locally available of all functions that are available in that rugby server. Cool huh? --Maarten
- Quoted lines have been omitted from some messages.
View the message alone to see the lines that have been omitted