TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Proportional Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
X-To:
"W. Wesley Groleau x4923" <[log in to unmask]>
Date:
Tue, 30 Nov 1999 19:35:30 +1100
Reply-To:
Subject:
From:
Geoff Bull <[log in to unmask]>
Content-Transfer-Encoding:
8bit
In-Reply-To:
Content-Type:
text/plain
MIME-Version:
1.0
Parts/Attachments:
text/plain (35 lines)
Quoting "W. Wesley Groleau x4923"
<[log in to unmask]>:

> > > > a little http server (it isn't that much work)
for Ada, ...
> > >    Looking at RFC 2616, "little" isn't the word
that comes to mind,
> > > even after tossing everything related to
cacheing.  What do you
> > > have in mind?
> >
> >
>
http://developer.java.sun.com/developer/technicalArticle
s/Networking/Webserv
> > er/index.html
> >
> > "The following code implements a simple,
multithreaded HTTP server in a
> > few hundred lines of Java code."
>
> It's not _just_ a few hundred lines of Java.  It's
about four hundred
> lines that make many more lines worth of API calls.
As many lines of Ada
> could easily make the same calls and probably more
reliably.
>
I get the impression that you think I was suggesting
that Java might be better than Ada for this. I wasn't.
I was suggesting that something similar could be done
in _just_ a few hundred lines of Ada. Of course the
_same_ API calls can be made if you use Cafe1815
(just as easily as Java, once I finish grinder).

ATOM RSS1 RSS2