In most cases the only thing that I have found helpful for debugging is lots
of data (maybe even a little data). Nothing tests your assumptions more than
lots of examples. I think the main reason is that code is tested with the
same dataset, found to be error free and then the developer moves on
On 9/5/06, John Buckman <[EMAIL PROTECTED]> wrote:
As to "why a debugger for aolserver"?
Any large web-based application shares many of the same complexity
problems of traditional applications, and from my C++ days, I learned
that I should never leave code in that I hadn't stepped through at
l
On Sep 5, 2006, at 6:00 PM, Jeff Hobbs wrote:
One thing I really miss in the Aolserver/Tcl world is a good debugger
-- "puts" isn't such a good alternative :D. Javascript, I believe,
has nice development environments and debuggers available. It'd also
be nice to have a wider world of source
On Tuesday 05 September 2006 12:42, Daniel P. Stasinski wrote:
> On 9/5/06, Tom Jackson <[EMAIL PROTECTED]> wrote:
> > I spent several hours fixing a bug with internal redirects, then found
> > out it had already been fixed.
> > If a status had been mapped to a url, then the server redirects
> > (i
On 9/5/06, Tom Jackson <[EMAIL PROTECTED]> wrote:
I spent several hours fixing a bug with internal redirects, then found out it
had already been fixed.
If a status had been mapped to a url, then the server redirects (internally)
to that url.
Can you elaborate more on this? I'm having a similar
Strange title, I know. But hear me out.
I talked before about creating easy to deploy "AOLserver
Applications". This is do-able the way I described it, but to do it
right, quite invasive in the core. And it probably still won't be
simple enough for people used to PHP deployments.
Here are
Sorry I was unclear. I was actually wondering whether or not we should just
merge with NaviServer so as to consolidate the code/user base.
-Titi
-Original Message-
From: Tom Jackson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 05, 2006 3:43 PM
To: AOLSERVER@LISTSERV.AOL.COM
Subje
FYI:
I did some more work on getting nsproxy to work under windows. The next
problem we run into is that it makes use of readv() and writev() which
are not directly available in windows. Some research that I did
indicates that some compilers have sort of "wrappers" for them but even
those m
On Tuesday 05 September 2006 11:06, Titi Ala'ilima wrote:
> How long ago did this fork take place? If AOL does indeed drop AOLserver
> and we rebrand it, are there any reasons other than the work involved to
> maintain a forked code/user base?
The current code is in very great shape. That means m
On 5 Sep 2006, at 18:54, Dossy Shiobara wrote:
Of course, non-AOL employees are free to speak and speculate all you
want. We just can't confirm or deny any of it.
Here goes my speculation then!
From between the lines in the past, I picked up that AOL business
units are getting a bit of freed
On 9/5/06, Titi Ala'ilima <[EMAIL PROTECTED]> wrote:
Rick Gutleber wrote:
> > 2) The biggest bang for our buck would be improving the Tcl language
> > and the codebase available for it rather than bringing in another popular
language. It took Rails to put Ruby on the map. What would our Rails
Nathan,
Any news on the nsdci module?
tom jackson
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
On 2006.09.05, Titi Ala'ilima <[EMAIL PROTECTED]> wrote:
> I mean improving the language as well. As Dossy said, there are a few
> things that could be added to the language that would "make the
> language geeks go 'ooh!'", and a few others that would just make life
> a little more powerful. This
How long ago did this fork take place? If AOL does indeed drop AOLserver and
we rebrand it, are there any reasons other than the work involved to maintain a
forked code/user base?
-Titi
-Original Message-
From: Bas Scheffers [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 05, 2006
[EMAIL PROTECTED] wrote:
On 5 Sep 2006, at 17:57, Titi Ala'ilima wrote:
1) AOLserver probably needs a new name. Something that uses the NS
initials would be ideal so that all those ns_* commands actually make
sense again. Could we resurrect the NaviServer name?
Already taken! (OpenSource fork
On 2006.09.05, Janine Sisk <[EMAIL PROTECTED]> wrote:
> On Sep 5, 2006, at 7:50 AM, Rick Gutleber wrote:
>
> >If AOL wants to sever its ties with AOLServer (and it looks like it
> >does)
>
> I am most curious about this statement. Does AOL truly want to move
> away from using AOLserver inter
On 2006.09.05, Jeff Hobbs <[EMAIL PROTECTED]> wrote:
> The Tcl Dev Kit Debugger should be able to be inserted into the
> AOLServer environment for effective debugging. You currently couldn't
> do that with Komodo, but if there was demand, we could make some
> modifications. However, TDK can handl
Rick Gutleber wrote:
> > 2) The biggest bang for our buck would be improving the Tcl language
> > and the codebase available for it rather than bringing in another popular
> > language. It took Rails to put Ruby on the map. What would our Rails be?
> >
> I would be careful to say "improve up
On 5 Sep 2006, at 17:57, Titi Ala'ilima wrote:
1) AOLserver probably needs a new name. Something that uses the NS
initials would be ideal so that all those ns_* commands actually
make sense again. Could we resurrect the NaviServer name?
Already taken! (OpenSource fork-without-anyone-from-AOL
On 5 Sep 2006, at 17:22, Jean-Fabrice RABAUTE wrote:
I have one webserver at home and only 1 public IP.
I have some web sites on PHP and some very few intranet pages on
aolserver/TCL.
I wanted to use aolserver, and virtual hosts.
I simply solve this (in various places) by having apache listen on
I spent several hours fixing a bug with internal redirects, then found out it
had already been fixed.
The code looks for an internal redirect in the case the return status
(404,500,etc.) indicates something besides OK.
If a status had been mapped to a url, then the server redirects (internall
Titi Ala'ilima wrote:
Gleaning from this conversation a few main points/questions, with a couple
cents of my own thrown in:
1) AOLserver probably needs a new name. Something that uses the NS initials
would be ideal so that all those ns_* commands actually make sense again.
Could we resurrec
One thing that might help is a feature chart of what PHP, Ruby etc have
that TCL/AOL don't.
This should include things like modules. I think there is a
misconception that PHP/Ruby et al have many more modules. They do but
most are absolute POS's. Written by teenagers with no real world
experien
On Tuesday 05 September 2006 08:41, Dossy Shiobara wrote:
> (Apologies for the long email ahead ... but, I think it's worth a quick
> read.)
All very well said! I have done a number of language surveys over the years to
find one that was thread-safe, fast and easy to extend. Tcl is the only one I
On Sep 5, 2006, at 7:50 AM, Rick Gutleber wrote:
If AOL wants to sever its ties with AOLServer (and it looks like it
does)
I am most curious about this statement. Does AOL truly want to move
away from using AOLserver internally (which would seem to be the case
if they want to sever ties
John Buckman wrote:
> Perl thread safety has never been properly debugged. In fact, that
> was the reason I moved from Perl to Tcl many years back. I had
> assumed that Python had fixed the global semaphore thing from when I
> looked at it 8 years ago, but no.
>
> Ok, Dossy, I buy your argum
Gleaning from this conversation a few main points/questions, with a couple
cents of my own thrown in:
1) AOLserver probably needs a new name. Something that uses the NS initials
would be ideal so that all those ns_* commands actually make sense again.
Could we resurrect the NaviServer name?
Perl thread safety has never been properly debugged. In fact, that
was the reason I moved from Perl to Tcl many years back. I had
assumed that Python had fixed the global semaphore thing from when I
looked at it 8 years ago, but no.
Ok, Dossy, I buy your argument that the other pop language
> Of course, the more popular languages weren't implemented
> with embeddability (embedibility?) in mind.
[...]
> safely embedded in a multi-threaded application.
I intended to reply to an earlier message regarding the suggestion that
we try to support PHP in AOLserver, but Dossy's observation
> On Tuesday, September 5, 2006 15:50, Rick Gutleber said:
> > Support for more popular languages (come on, let's say it together, I
> > know it's hard, but "Tcl is not popular") is probably the most useful
> > long-term technical change that can be made. This isn't an indictment
> As long as it i
This has been a pretty wide ranging discussion, now I'm starting to wonder a
little bit, maybe worry a little bit.
There seems to be at least one misconception about the product AOLserver,
which should be put to rest:
That is about language choice and the ability of introducing new scripting
l
[EMAIL PROTECTED] wrote:
(Apologies for the long email ahead ... but, I think it's worth a quick
read.)
On 2006.09.05, Rick Gutleber <[EMAIL PROTECTED]> wrote:
Support for more popular languages (come on, let's say it together, I
know it's hard, but "Tcl is not popular") is probably the most
On Tuesday, September 5, 2006 15:50, Rick Gutleber said:
> Support for more popular languages (come on, let's say it together, I
> know it's hard, but "Tcl is not popular") is probably the most useful
> long-term technical change that can be made. This isn't an indictment
As long as it is anything
(Apologies for the long email ahead ... but, I think it's worth a quick
read.)
On 2006.09.05, Rick Gutleber <[EMAIL PROTECTED]> wrote:
> Support for more popular languages (come on, let's say it together, I
> know it's hard, but "Tcl is not popular") is probably the most useful
> long-term techn
If AOL wants to sever its ties with AOLServer (and it looks like it
does) then a name change is probably in order. It's a shame because
there are good reasons for each to be associated with the other by
name. From my limited experience, I think the tool has benefitted from
tremendous talent a
On 2006.09.05, Bas Scheffers <[EMAIL PROTECTED]> wrote:
> What about the website? I *really* think we should move this to AOLserver;
> we have to practice what we preach! Maybe just go with OpenACS? Any
> experts on that who would want to be technical lead on that? If hosting is
> a problem (I hope
On Sunday, September 3, 2006 16:58, John Buckman said:
> 2) there is lots of good competition - everything from Ruby, Python
> and Zope to LightHttpd is in the same kind of mind space --
> alternatives to Apache that have cool ideas in them.
Well, half of those actually run inside Apache, they are
37 matches
Mail list logo
