On Tue, Jun 01, 2004 at 06:09:44PM -0400, Dossy wrote:
On 2004.06.01, Francesco P. Lovergine [EMAIL PROTECTED] wrote:
Greetings from your Debian GNU/Linux AOLserver series maintainer.
Your great news are welcome.
Thanks, Frankie!
I added a couple of patches which are required to have a
Greetings from your Debian GNU/Linux AOLserver series maintainer.
Your great news are welcome.
On Thu, May 20, 2004 at 01:52:47PM -0400, Dossy wrote:
3) SourceForge bug and support trackers
There are currently 56 open bugs, 3 open support requests, 29 open
patches and 8 open feature
Thanks Jeff! I'll try and post something to this list by then end of the week.
- Nathan
Jeff Hobbs wrote on 5/21/2004, 5:14 PM:
We would be willing to add to our docs whatever is necessary to
clearly indicate to users how to use it specifically with
AOLServer.
--
AOLserver -
Hi Talli,
bah. i'm sick of the we need php/python/brainfuck in AOLserver to be
successful and gain mindshare.
hm. it was a discussion about strategy (the focus). Of course it's easier to
abort that discussion and directly start with graphic design and IA.
And when it comes to the marketing
Dossy wrote:
Yes, I definitely plan to communicate with the AOLserver Community as to
what is going on, what plans are being made, what our progress is
towards the goals set forth in the roadmap, upcoming releases, and so
on.
I welcome anyone to call me on this if they feel that there are
On Thu, 20 May 2004, Dossy wrote:
1) www.aolserver.com website revamp
The project website deserves a more modern look and feel while
maintaining the crisp, clean design aspects of the site. The site
needs to clearly represent the most current releases and recent
changes.
- It's not L.A.M.P. People are sceptical to changes of the way of doing
things and often act like sheep.
and
Clearly AOLservers biggest competitor is PHP. Were the current website
falls short is to explain why people need to choose AOLserver over
Apache/PHP. I.e.:
PHP works with
On Fri, 21 May 2004, Bernd Eidenschink wrote:
PHP works with AOLserver, at least some folks use it. I don't know how
well maintained the bridge ist, nor if PHP can be compiled with 4.0, but
supporting PHP would be absolutely no harm. I would think of it as the
honeypot. It would allow people
On Fri, May 21, 2004 at 11:10:31AM +0200, Dani?l Mantione wrote:
On Fri, 21 May 2004, Bernd Eidenschink wrote:
PHP works with AOLserver, at least some folks use it. I don't know how
well maintained the bridge ist, nor if PHP can be compiled with 4.0, but
supporting PHP would be absolutely
Hi Daniel, Bas,
I agree with most of your arguments. But I don't think we should think
of AOLServer as a pathetic wannabe should it allow to combine it with
PERL, PHP, HypeXY: If you don't need it, don't use it. People will
notice that use of TCL is superior for many things but they are not
bound
Strangely enough, I have never been able to connect to freenode while
at the AOL offices. The DNS lookup succeeds, but the connections are
always refused. In order to connect, I have to proxy my IRC connection
through some other co-lo servers I have back at the University I
attended.
So I'm not
On Fri, 21 May 2004 10:58:02 +0200
Bernd Eidenschink [EMAIL PROTECTED] wrote:
PHP works with AOLserver, at least some folks use it. I don't know how
well maintained the bridge ist, nor if PHP can be compiled with 4.0,
Yes, it can. I recently built it using AOLServer 4.01 and PHP
On Friday 21 May 2004 15:35, Bob Woodside wrote:
insight into why Dossy said that moving back to an AOLserver is not at
the top of the priority heap, but takes a back seat to revamping the
site's content.
Content??? What content?
Zoran
--
AOLserver - http://www.aolserver.com/
To Remove
On 2004.05.21, Daniël Mantione [EMAIL PROTECTED] wrote:
The message to new users should be Yes. You have to switch to TCL, but,
don't worry, we're sure you'll regret that you didn't do it before
instead of Switch to AOLserver, it's easy and nothing has to change for
you.
See, I disagree here.
On May 21, 2004, at 11:11 AM, Dossy wrote:
The learning curve is a big hurdle to technology adoption. Flattening
that curve by letting folks migrate to AOLserver while maintaining
their
current levels of productivity ... will only ease the pain of
migration.
The thing we don't tell them up front
On Fri, 21 May 2004, Dossy wrote:
On 2004.05.21, Daniël Mantione [EMAIL PROTECTED] wrote:
The message to new users should be Yes. You have to switch to TCL, but,
don't worry, we're sure you'll regret that you didn't do it before
instead of Switch to AOLserver, it's easy and nothing has to
On Fri, May 21, 2004 at 05:11:35PM +0200, Dani?l Mantione wrote:
On Fri, 21 May 2004, Bob Woodside wrote:
The problem here is that www.aolserver.com is just an alias for
vhost.sourceforge.net. Since the site is actually hosted on SourceForge,
AOL haven't got control over what Web
Ok, fine with me! But, if you want to tell this to your potential users,
you must also give them a reason to switch. If the reason to switch
is not to use TCL and use the AOLserver API, what is it? Users won't
switch because they can leverage the vast knowledge they already have,
for the
On Fri, 21 May 2004, Bernd Eidenschink wrote:
Ok, fine with me! But, if you want to tell this to your potential users,
you must also give them a reason to switch. If the reason to switch
is not to use TCL and use the AOLserver API, what is it? Users won't
switch because they can leverage
Ehrm, Sourceforge doesn't own aolserver.com and whoever does can point
the DNS records to anywhere, including an AOL server running AOLserver!
Bas.
Andrew Piskorski said:
On Fri, May 21, 2004 at 05:11:35PM +0200, Dani?l Mantione wrote:
On Fri, 21 May 2004, Bob Woodside wrote:
The
On Fri, 21 May 2004, Bas Scheffers wrote:
Then they shouldn't be writing those bugs in the first place! ;-)
Sorry but this is complete nonsense and often said by people who never
used a good debugger.
I have never used any debugging tools other than puts or
System.out.println(), never needed
I've found good unit testing to be a very reliable way to avoid code
bugs in the first place and, though I haven't used it in a long while,
TclPro was a good debugging system for tcl code. I'm not sure where it
stands now, but could it be used with AOLServer to step through tcl code?
Rob Seeger
On 2004.05.21, Daniël Mantione [EMAIL PROTECTED] wrote:
See, I disagree here. The message should probably be something like:
Switch to AOLserver, you'll be able to leverage the vast knowledge you
already have and be as productive as you already are. Then, as you
learn more and more Tcl
Daniel, we are not exactly writing a compiler in Pascal or C here, are we?
All we do is do a couple of database queries and format some text. In my
Java work I do a bit more, like propriatary protocols on TCP/IP, bit more
working with files, some threads and that sort of stuff. But all in the
bah. i'm sick of the we need php/python/brainfuck in AOLserver to be
successful and gain mindshare.
i'm really quite sick of this argument that AOLserver is hard to pitch.
i personally have no problem doing so whatsoever. in fact, i usually
win projects on the sole basis that we are wizards in
On Fri, 21 May 2004, Dossy wrote:
No, the point is that in the future they WILL learn and use Tcl, but in
order to make the initial switch, they don't HAVE to start from scratch
and spend a long time climbing the learning curve before they can feel
really productive again.
Ok, that's a good
On 2004.05.21, Talli Somekh [EMAIL PROTECTED] wrote:
i find that in these situations it's usually best to set an expiration
date on these things, so the offer stands until the end of the business
day EST a week from today.
More important than an expiration date is a due date. When can you
TclPro can be used with AOLserver, including the 4.x versions. Jim added the hooks a
long time ago. I can try to put together some instructions if folks are interested.
It's nice, but a lot slower then simply adding a bunch of ns_log statements in your
code. ;-)
- Nathan
Robert Seeger wrote
Nathan Folkman wrote:
TclPro can be used with AOLserver, including the 4.x versions. Jim added the hooks a
long time ago. I can try to put together some instructions if folks are interested.
That would be very helpful. I would definitely appreciate any hints on
how to use TclPro with AOLserver.
Nathan Folkman wrote:
TclPro can be used with AOLserver, including the 4.x versions. Jim
added the hooks a long time ago. I can try to put together some
instructions if folks are interested.
That would be very helpful. I would definitely appreciate any
hints on how to use TclPro with
On Fri, May 21, 2004 at 03:54:16PM -0400, Nathan Folkman wrote:
TclPro can be used with AOLserver, including the 4.x versions. Jim
added the hooks a long time ago. I can try to put together some
instructions if folks are interested. It's nice, but a lot slower
then simply adding a bunch of
I have tried Tcl Dev Kit 3 recently and while it worked for the first
connection to AOLserver, the Tcl debugger locked up AOLserver at the end of
that connection.
I followed the instructions at http://www.tcl.tk/man/aolserver3.0/tadp-ch6.htm
/Bart
--
AOLserver - http://www.aolserver.com/
To
Hi,
I would like to formally announce that effective immediately, Dossy
Shiobara will be taking over the role of Project Leader for AOLserver. He
will be responsible for all aspects of the project, ensuring that it continues
to move forward and gets the attention it currently needs to
Congratulations Dossy!
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 2004.05.20, Jim Davidson [EMAIL PROTECTED] wrote:
Expect to see a communication from Dossy himself regarding the upcoming
plans and goals for the project.
Thanks, Jim. I suspect this announcement comes as sort of a surprise to
everyone as the list and project have been fairly quiet in the
On 2004.05.20, Dossy [EMAIL PROTECTED] wrote:
I'll be posting the roadmap to the wiki shortly, but for now, here it
is:
FYI,
http://panoptic.com/wiki/aolserver/Roadmap
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web:
Oh, one more... Would it make sense to look at doing .NET integration using work being
done on the Mono project? That way it could theoretically be leveraged across
different OS's, not just Windoze.
http://www.go-mono.com/
- Nathan
Dossy wrote on 5/20/2004, 1:52 PM:
While we shouldn't be
Uytkownik Dossy napisa:
On 2004.05.20, Jim Davidson [EMAIL PROTECTED] wrote:
Expect to see a communication from Dossy himself regarding the upcoming
plans and goals for the project.
Thanks, Jim. I suspect this announcement comes as sort of a surprise to
everyone as the list and project have
There is a beta NSS/NSPR module checked into soureforge, the nsnss
module. Should work ok but so far nobody that I know of has used it in
production.
rob
Nathan Folkman wrote:
Congratulations!
I was wondering if there were any plans to start up the weekly AOLserver chats again,
and also what are
Hopefully I can clear up a few things here... :-)
First off, Dossy actually now works for AOL in Jim Davidson's group. I was chatting
with some other folks in the AOLserver Community recently, and there seemed to be a
little confusion about how and why he was chosen to lead the project. Dossy
On 2004.05.20, Tomasz Kosiak [EMAIL PROTECTED] wrote:
I would like to see clear message from new leader about what has happend
and what is current status of the project.
I really don't want to dwell on the past and everyone who has been
following AOLserver knows where things have been over the
I recently setup an aolserver room at irc.freenode.net. Hardly anyone hangs
out there these days, but the conversations there are being logged and are
available from http://www.thecodemill.biz/services//aolserver/irc/.
Maybe that IRC would be a viable alternatice to AIM?
/Bart
--
AOLserver -
42 matches
Mail list logo
