There are two reasons.
1. Distributed development has its merits, mainly, you don't have to
coordinate. It also has the drawback you noticed: it allows lack of
coordination.
2. Historically AOLServer team and keepers of SF project have been
absolutely unacommodating to the needs of what we like
1.0.
It lets small pages get out, just not ones that drag their feet talking to the
database.
uname -a
NetBSD planning.local 1.5 NetBSD 1.5 (GENERIC) #1: Sun Nov 19 21:42:11 MET 2000
fvdl@sushi:/work/trees/netbsd-1-5/sys/arch/i386/compile/GENERIC i386
pkg_info | grep nsopenssl
nsopenssl-1
Actually, looking at your log output, your conn is being cut immediately.
Still need to know what version of nsopenssl you're running.
> Ian,
>
> what version of nsopenssl are you using? Can you time how long before your
> conn is cut?
>
>
> /s.
>
> On Fri, 9 Nov 2001 10:50:50 -0800, Ian Harding
Ian,
what version of nsopenssl are you using? Can you time how long before your
conn is cut?
/s.
On Fri, 9 Nov 2001 10:50:50 -0800, Ian Harding <[EMAIL PROTECTED]> wrote:
>I have nsopenssl working fine with one exception. If the page takes 'too
long' to serve up, nsopenssl closes the connect
Scott, I don't know the answers to any of your questions (and they are some
good ones). But I would like to point out that these are precisely the
things that damage AOLserver's attractiveness to the "unwashed masses" who
operate on Win32, and also those of us who are in the know, but still have
Where is the latest ns* module? Why do I have to manually edit a module's
Makefile? Why are these modules scattered all of the net? How come we have
the same module in multiple places? Why does the coding style in one module
look completely different than the coding style for another module? Why d
Jerry is correct.
And so is Patrick.
And so is Mike.
--
Mark Hubbard: [EMAIL PROTECTED]
Microsoft Certified Professional
"Never apply a Star Trek solution to a Babylon 5 problem."
-Original Message-
From: Mike Hoegeman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date
Patrick Spence wrote:
>
masses..
> >
> > i think the real "competitor" to aolserver is apache and if apache runs
> > on windows but aolserver does'nt.. it becomes a harder sell..
>
> But the real point is that AS isn't a product.. its a piece of software
> that we are reaping the benifits of usin
- Original Message -
From: "Mike Hoegeman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 09, 2001 11:21 AM
Subject: Re: [AOLSERVER] AOLserver 4 - Win32 not supported?
> Jerry Asher wrote:
> >
> > The decision to drop Win32 has been kicking around for some time now.
>
I have nsopenssl working fine with one exception. If the page takes 'too long' to
serve up, nsopenssl closes the connection too soon.
I have read what I can find and can't fix it.
Any ideas?
log snippet...
[08/Nov/2001:21:01:20][28846.43][-conn3-] Notice: dbdrv: opening database
'postgres:l
Jerry Asher wrote:
>
> The decision to drop Win32 has been kicking around for some time now.
>
> My interpretation of the chat two weeks ago was that dropping Win32 support
> should make it easier to make AOLserver more robust and maybe faster in the
> UNIX environments. It will definitely make i
As a user of a mixed NT/Linux environment, the decision to drop Win32 is a
bit of a bummer for me and my employers. We're now left with IIS and maybe
Apache. But the group's logic makes sense, especially the part about having
a miniscule user base in the Win32 world, and that situation continuin
Support Requests item #480111, was opened at 2001-11-09 09:52
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=203152&aid=480111&group_id=3152
Category: Configuration: Other
Group: aolserver3_3_1
Status: Open
Resolution: None
Priority: 5
Submitted By: Gabriel Borragei
The decision to drop Win32 has been kicking around for some time now.
My interpretation of the chat two weeks ago was that dropping Win32 support
should make it easier to make AOLserver more robust and maybe faster in the
UNIX environments. It will definitely make it an easier application to
sup
Microsoft will always own the NT server market and there will be a
miniscule following for AS on NT. A survey would likely show that the
number of active AS users (users, not IP addresses) is already tiny
compared to Apache and IIS. As a product with a smallish audience, it
makes a lot of sense
Mike,
I found the problem almost right after I sent the mail. It's Solaris
2.7, there's no core file and the server keeps running. It was a problem
with the Sybase proxy daemon.
Thanks,
Kevin
In a message dated 11/9/2001 12:04:51 AM Eastern Standard Time,
[EMAIL PROTECTED] writes:
> >
Support Requests item #48, was opened at 2001-11-09 05:39
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=203152&aid=48&group_id=3152
Category: Configuration: First-Time Startup
Group: aolserver3_2
Status: Open
Resolution: None
Priority: 5
Submitted By: Danny
Cygwin is a great toolkit, and I heartily recommend it to anyone
who is used to working on Unix. But I would like to see AOLserver 4
continue to run natively under Win32. In addition to Cygwin taking
up disk space and adding another layer of debugging / installation /
configuration
complexity
18 matches
Mail list logo
