> I was thinking about this also. There is a nsmemcache module for
> naviserver, but it uses some of the C apis that have been changed
> slightly in naviserver, so it doesn't work with aolserver, but it
> shouldn't be difficult to port.
memcached is lovely, but what makes ns_cache so fast is th
John Buckman wrote:
> SUGGESTIONS FOR A FUTURE AOLSERVER
>
> The "state of the art" is, I think, happening in the javascript world,
> with things such as node.js. If the aolserver community were really
> interested in getting new users, making it a top notch
> embedded-javascript web server would b
jgdavid...@mac.com wrote:
>
> and those NS_IMPORT/NS_EXPORT
> declarations.
Those are less of a windows-only thing now. Some recent version of gcc
introduced visibility attributes which are supposed to be super good for
improving link times or something like that, so unix with a new-enough
gcc
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
Howdy,
The point about libraries only available on Windows is a compelling reason for
some support, given it mostly works today.
Honestly, AolServer isn't so bad at supporting Windows. I wrote most of the
cross-platform code and was able to smash down quite a bit of the differences.
The ap
SUGGESTIONS FOR A FUTURE AOLSERVER
The "state of the art" is, I think, happening in the javascript world, with
things such as node.js. If the aolserver community were really interested in
getting new users, making it a top notch embedded-javascript web server would
be a way. I'm not sure this
On the apache vs aolserver topic, I just want to mention that we've been
migrating sites *off* of Apache/PHP/Perl, and onto aolserver, for the past 2
years.
http://moodmixes.com/ was launched last year, http://ilicensemusic.com/ a few
weeks ago, and we're currently rewriting http://magnatune.co
Naviserver has added a lot of interesting features, and appears to be fairly
mature.
I would have probably switched to Naviserver two years ago if they had
documented some of their changes. The quantity of the contributions, and the
interesting nature of many of them, make me feel that Naviser
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
Has anyone analyzed Naviserver performance and features vs. AOLserver
lately?
It appears to remain compatible with Windows.
The following forum post suggests Naviserver may be a contributing
factor to a significant overall performance increase:
http://openacs.org/forums/message-view?message_id
On Wed, Sep 26, 2012 at 09:07:07AM -0600, jgdavid...@mac.com wrote:
> Should we dump the Windows port in favor of a clean Unix code base,
> configure, build, and install?
Cross-platform portability is very Nice to Have, and I've actually
used it. Fortunately I've never had to deal with or even l
It appears there is enough consternation about removing Windows support that I
doubt figuring out how to run AOLserver on Windows sans the Windows-specific
code in the codebase would result in having the Windows code removed anyway, so
I am rescinding my suggestion that we find a way to do so.
Hi!
I believe that it is important to consider the current
phase of the "live cycle" of AOLserver in order to focus
the roadmap on the important stuff:
- AOLserver is "mature" software, there were relatively
few changes in the last few years. There are very
large productive installations re
First, Jeff thanks for initiating this thread...all the ideas seem good. One
note below.
- Original Message -
> From: Jeff Rogers
> To: Ayan George
> Cc: aolserver-talk@lists.sourceforge.net
> Sent: Wednesday, September 26, 2012 9:28 AM
> Subject: Re: [AOLSERVER] Roadmap - 4.6 and beyo
Dear all,
I do not think that removing Windows specific code is a good idea.
Some time ago I showed as example how many people have downloaded
]project-open[ on Windows as opposed to the VM, or the tar ball.
In case you do not remember the numbers, please have a look at this URL:
http://sou
Hi!
I've cleaned up our websockets code a bit (ah, the joy of it), it should
run now on a basic AOLserver install. Where should I post it?
Wolfgang
--
digital concepts OG
Software & Design
Landstrasse 68 / 5. Stock
A - 4020 Linz
Büro: +43 732 99711772
Mobil: +43 699 19971172
--
17 matches
Mail list logo
