TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced 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]>
Subject:
From:
Tom Moran <[log in to unmask]>
Date:
Wed, 1 Dec 1999 11:20:55 -0700
Reply-To:
Tom Moran <[log in to unmask]>
Parts/Attachments:
text/plain (11 lines)
  A situation in which an embedded system communicates to public
outside systems via HTTP & HTML would seem a logical candidate
for an embedded, custom, server.  It might call internal
routines instead of using the CGI mechanism, for instance.
It might be reasonable to skip support of some HTTP things,
in which case, as has been demonstrated, it could be quite
small and easy to create.  It could be carefully vetted,
which might be rather more tedious with a full-up COTS server.
  I find it more difficult to imagine scenarios where a
custom browser of limited capability would be as worthwhile.

ATOM RSS1 RSS2