From: Lucas Gonze (firstname.lastname@example.org)
Date: Fri Aug 18 2000 - 12:07:41 PDT
> Proxies were an afterthought; SOAP doesn't consider them. Result:
> SOAP over HTTP su... er, has technical difficulties.
IMHO this is the elephant that HTTP-as-substrate fans don't think about.
(obscure analogy to old nun technique for avoiding lustful desires:
"Whatever you do, don't think about an elephant". My aunt, who is a saucy
old bohemian, loves this quote.)
Wait! I almost missed a chance to expound! Tarnation! This is the reason
why HTTP should be the fallback, not the default, for anything but browser
messages. EG if there is a chain of communications A->B->C->D, and one of
those links has to use HTTP, the rest of the comms should be a more
robust/modern protocol. HTTP should always be available for legacy
compatibility but only used when legacy compatibility is required.
I'm posting way too much lately. Over and out.
This archive was generated by hypermail 2b29 : Fri Aug 18 2000 - 09:18:13 PDT