From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Gary Thomas <gthomas@ecoscentric.com>
Cc: rhea santos <marheas@asti.dost.gov.ph>,
eCos Discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] GoAhead Web server
Date: Wed, 20 Nov 2002 00:59:00 -0000 [thread overview]
Message-ID: <20021120085922.GD20349@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <1037782228.11772.18.camel@localhost.localdomain>
On Wed, Nov 20, 2002 at 01:50:27AM -0700, Gary Thomas wrote:
> On Mon, 2002-11-18 at 22:52, rhea santos wrote:
> >
> > hi!
> > I would like to ask if anyone here had already tried to use the open source
> > GoAhead Web Server using assabet and eCos? What was your experience in
> > building the application ? How was the support for GoAhead ? How did it
> > perform ?
> >
>
> We have run this server, but it was many years ago. I've not
> tried it recently, but that older version ran fine.
I played with it a few months ago. It seemed rather slow, but i never
spent the time to work out why.
I also had problems with GoAheads built in ROM file system when used
with Lynx. Lynx added a leading /. I don't remember which, but it
caused the ROM filesystem to fail to find the file. This worked OK for
Nutscape.
Andrew
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2002-11-20 8:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-19 12:53 rhea santos
2002-11-20 0:53 ` Gary Thomas
2002-11-20 0:59 ` Andrew Lunn [this message]
2002-11-20 1:14 ` sandeep
-- strict thread matches above, loose matches on Subject: below --
2004-05-23 23:18 [ECOS] goAhead web server baljeet singh
2004-05-24 7:21 ` mohanlal jangir
2002-11-20 9:07 [ECOS] GoAhead Web server Anthony Massa
2000-10-25 16:25 [ECOS] GoAhead Web Server amassa
2000-10-25 17:01 ` Gary Thomas
2000-10-25 15:14 amassa
2000-10-25 15:35 ` Gary Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021120085922.GD20349@biferten.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=gthomas@ecoscentric.com \
--cc=marheas@asti.dost.gov.ph \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).