[REBOL] Re: Any changes re dbases in upcoming RT products?
From: petr:krenzelok:trz:cz at: 2-Oct-2001 21:14
----- Original Message -----
From: <[holger--rebol--com]>
To: <[rebol-list--rebol--com]>
Sent: Tuesday, October 02, 2001 8:49 PM
Subject: [REBOL] Re: Any changes re dbases in upcoming RT products?
> On Tue, Oct 02, 2001 at 08:26:56PM +0200, Petr Krenzelok wrote:
> > That's not true imo. Look at docs - with both static and dynamic configs
you
> > can use -processes X, where X is number of processes. Although it is a
> > little bit static, you can allocate X processes for each URL imo. Other
> > thing is, that Session Afinity patch is available for FastCGI, so it
will do
> > some kind of load balancing for you, or at least assign one session ID
to
> > the same process. Session afinity patch is coming to be default part of
> > FastCGI distro, but we already know it will not help us, as RT uses own
> > FastCGI implementation.
>
> I would assume such a patch to affect the web server only, so it would
> work with REBOL in the same way as with other programs.
>
> > I am stuck with Windows Apache version - Windows /Command allows usage
of
> > only External FastCGI server set-up. But pressing reload button on
browser
> > quickly two times crashes FastCGI listen loop. If I will not solve it,
then
> > I can regard FastCGI not being functional at all under Windows ...
>
> Crashes how ?
I already reported it to feedback some time ago and also asked for
participation of folks here on ml. No response though. So - I use simple
loop found in your FastCGI docs. I parse out requested html file and do it,
e.g.:
http://my.domain.com/fcgi-bin/invoices.fcgi
so the code results in do %invoices.fcgi ... where I look if ODBC connection
is already set-up, and if not, I do open
one. Then I do some select, taking some time ...
If I do everything in sequential manner, e.g. in rebol console: read
http://my.domain.com/fcgi-bin/invoices.fcgi, everything is OK, - Rebol
handles for me 3 rather complex queries per second. It is 34 kb of data per
request. But - once I press reload button two times quickly, main FastCGI
loop crashes on strange timeout bug ... I assume some user can double click
on reload and I've got a problem ... Any hints here? I tried it on Win2K
Apach External FastCGI set-up.
Thanks,
-pekr-
