stack" point of view.
Here I end,
Maurizio
-Original Message-
From: Gustaf Neumann [mailto:neum...@wu.ac.at]
Sent: 29 September 2012 14:31
To: aolserver-talk@lists.sourceforge.net
Subject: Re: [AOLSERVER] Windows Support
Maurizio,
the mentioned thread in the OpenACS forum is about
Maurizio,
the mentioned thread in the OpenACS forum is about speed,
not functionality. The issue came up for large sites when
postgres changed the rules for their optimizer. I would think
that most OpenACS sites work fine with current pg versions.
The 9.* support is in OpenACS CVS since July las
Jeff,
i fully agree with you that this would be the right
direction and a
win-win situation for both communities. This would be however
not only a question of "turning the build setup", but a
substantial
amount of rewriting of e.g. the i/o and threading layers.
A few years ago i have looked a l
support the latest versions
of PostgreSQL.
I hope to have been clearer this time.
Maurizio
==
-Original Message-
From: Gustaf Neumann [mailto:neum...@wu.ac.at]
Sent: 29 September 2012 12:54
To: aolserver-talk@lists.sourceforge.net
Subject: Re: [AOLSERVER] Windows Support
ginal Message-
>
>
> From: Jeff Hobbs [mailto:je...@activestate.com]
> Sent: 29 September 2012 02:53
> To: aolserver-talk@lists.sourceforge.net
> Subject: Re: [AOLSERVER] Windows Support
>
> It is likely quite possible to turn things around and have AOLServer be a
> set of extensions
t: Re: [AOLSERVER] Windows Support
It is likely quite possible to turn things around and have AOLServer be a
set of extensions that load into a standard tclsh. The state of extensions
is pretty open, and again if more of the Tcl standard code can be leveraged
(socket handling, threading, etc.), this would
It is likely quite possible to turn things around and have AOLServer be
a set of extensions that load into a standard tclsh. The state of
extensions is pretty open, and again if more of the Tcl standard code
can be leveraged (socket handling, threading, etc.), this would be a
good thing. Afte
How about making AolServer nothing more than a TEA-compliant extension? Maybe
we could create an "ns_main" command that created a thread that did all the
AolServer stuff (i.e., listen on sockets, create connection pools, etc. etc.)
and just run it in tclsh.
I never looked at TEA close enoug
Maurizio Martignano wrote:
> Dear all,
> I do not think that removing Windows specific code is a good idea.
Hi Maurizio,
You make a good argument for keeping windows support. There is a cost
of some added complexity, but I don't think that's unreasonable.
The biggest challenges are keepi
On 2012-09-27, at 1:56 AM, Maurizio Martignano
wrote:
> So what are the feasible options?
> I believe there are only two (well three) options:
> 1. we maintain the Windows code inside Aolserver (I favour this)
> 2. we compile Unix only code via the SUA SDK
> 3. we forget about Windows and we use
10 matches
Mail list logo
