Re: Proposed issue; Visibility of Web services

> Do you realize that what I mean by a "generic intermediary" is one
> that we could code today, deploy, and then never change again?  As
> Walden described, how well would a generic SOAP intermediary do in
> understanding the interaction between some SOAP application produced in
> the future?  How well would a generic HTTP intermediary do?
> 
> I'll cut it off there, if that's ok.

That's fine. :-)

But I'd like to segue briefly in to my question about cost, because
I believe the answer to the SOAP question about will be that the
SOAP intermediary will be configurable using Xpath expressions
or whatever.

That amounts to pushing what is essentially a programming task "out"
to a place where it is likely to be widely distributed and unlikely
to under sufficient configuration management. I've seen this before,
so I'm leery.  Please don't ignore the cost of managing such a system
when "calculating" visibility.

Thanks,
Walden