All,

I have followed this thread with interest over the past couple of days,
but since we are not yet actively developing JSP applications, I have
stayed out of the fray.  However, since the conversation has strayed
somewhat from JSP per se, I think I have some salient points to offer.

I think that saying "HTML and HTTP are so tightly bound that ... [they]
are considered integral", is sort of like saying that since most
gasoline is consumed by cars that only cars are an effective use of
gasoline.  Most people consider them integral only because of the common
usage.  Extrapolating the above has a specific name in logic theory, but
I don't remember what it is (too many years since I took the class ;-).

We (and many of the largest sites) use HTTP extensively outside the
context of HTML.  We use it for the delivery of XML in B2B
communication, delivery of images and other binary content between
systems, and for tunneling batch up/downloads across a firewall.  In
fact, non-HTML HTTP traffic is a substantial portion of our bandwidth
utilization.

Conversely, there are plenty of examples of non-HTTP HTML usage.  HTML
documentation received on many CD-ROMs is one.  HTML is a language that
specifies a presentation layer syntax and is commonly, but not
exclusively delivered by HTTP.

All that being said, there is no question that both standards had their
genesis in solving the same problem.  Fortunately, the CERN staff had
the foresight to develop both standards independently and with an eye
towards openess that has led to innumerable clever implementations by
innumerable clever people.  Without this, many of us, myself included,
would not be employed in this industry.

J

Arthur Alexander wrote:
>
> My apologies to the group
> ( thanks Craig and Costin for pointing it out).
>
> I did indeed mean HTTP specification, yet I think
> that my meaning was the same.  HTML and HTTP are
> so tightly bound that the specifications are, for
> the most part, considered integral.
>
> What mechanics are there for viewing HTML that
> does not utilize HTTP?  Very few I would bet.
> How many clients utilize HTTP and do not
> expect content that conforms to the HTML spec,
> of course with other embed's.?  Again I think
> the honest answer is very few indeed.
>
> Sounds to me like you have all of the mechanics
> you need for your dynamic XML construction/parsing
> in the Servlet class mechanics Craig.  The only
> reason for looking for a script based extension (JSP?)
> that I seem to hear is providing another, possibly
> easier to access mechanism that a Servlet.

--
 *#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*
  *#
   *#   Joe Wilson         WashingtonPost.Newsweek Interactive
    *#   (703) 469-2644     Manager, Technology Applications
     *#   (703) 469-2995     1560 Wilson Blvd, Arlington, VA  22209
      *#
       *#   He who can no longer pause to wonder and stand rapt in awe,
        *#   is as good as dead; his eyes are closed. --Albert Einstein
         *#
          *#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to