Webware for Python

On Mon, 2002-08-26 at 05:25, Fionn Behrens wrote:
> 
> Hi all,
> 
> I know virtual domain setups have been discussed several times in the past but
> I would like separate configuration (especially separate error messages) and
> (error-) log files for each virtual domain.
> Imagining a split setup with 10+ threads for each virtual domain is not a
> satisfying thought either.
> I wonder if expwebware (Hi Tavis) could help me in that case but I get it that
> it has no working MiddleKit and it looks like the CVS has not been touched in
> the last months by any developer anyway.

Really, the only way to do it with (non-exp) Webware is with
MakeAppWordDir, i.e., different AppServers, and more threads.  You can
turn the number of threads down, especially if you don't expect lots of
traffic.  I don't think the overhead should be that bad, except in terms
of memory.  The actual threads themselves shouldn't be that much of an
overhead.

Otherwise you have to share configurations, though with a little hacking
you might be able to fix certain things of importance to you (like,
perhaps, making the configuration for error messages be per-context).

  Ian

Hi Fionn,
On August 26, 2002 03:25 am, Fionn Behrens wrote:
> Hi all,
>
> I know virtual domain setups have been discussed several times in the p=
ast
> but I would like separate configuration (especially separate error
> messages) and (error-) log files for each virtual domain.
> Imagining a split setup with 10+ threads for each virtual domain is not=
 a
> satisfying thought either.
>
> I wonder if expwebware (Hi Tavis) could help me in that case but I get =
it
> that it has no working MiddleKit and it looks like the CVS has not been
> touched in the last months by any developer anyway.

Actually I have been working on it, but not using the public CVS on=20
sourceforge.  I've been rather busy with work projects so I've been keepi=
ng=20
my mouth shut about expwebware until I have a chance to put some serious=20
hours into it and finish off the compatibility stuff I promised months ag=
o. =20
When time permits ...

Anyway, like Ian wrote, at present the best solution to your problem  is =
to=20
run a separate appserver for each virtual domain.  Security is also bette=
r=20
this way, particularly if you use a separate user account for each instan=
ce=20
of the appserver.  The only noticeable overhead would be the extra memory=
=20
requirements.  But, memory's cheap these days.

Cheers,
Tavis