[
Lists Home |
Date Index |
Thread Index
]
Hi,
I just finished reviewing the Proposed Architecture on your site, and
there is a lot of good information here. I wanted to provide feedback
without subscribing to the group (I hope it's ok that I do so here).
The biggest question I have is: why are new HTTP headers being proposed?
I ask for several reasons:
(1) It seems to me that it might be difficult (logistically,
politically) to add new headers to the HTTP protocol, although I may be
very wrong on this.
(2) From a technical standpoint, if new HTTP headers are added, how will
existing implementations of HTTP servers and clients be affected? Will
the new headers be "transparent" to them? Or, will there be adverse
effects unless the implementations are updated to "recognize" (even if
they ignore) these new headers?
(3) Adding new HTTP headers means that Web services that are transported
over other protocols (UDP, BEEP, TCP/IP, to name a few) will not benefit
from this approach.
(4) I believe the Web services world (partly for the reason in #3 above)
is moving away from relying on the underlying transport mechanism for
specific functionality, and is instead specifying this functionality in
the Web services specifications themselves. For example, in WS-Routing
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnglobspec/html/ws-routing.asp
- part of the Microsoft Global XML Web Services Architecture initiative,
or GXA), the placement of destination addresses for a Web services
message route is specified in the SOAP header, because HTTP cannot
provide this level of routing capability. WS-Routing also makes SOAP
more protocol-independent by specifying placement of destination
addresses in the message header to create a route for the message to
take.
Kind Regards,
Joe Chiusano
Booz | Allen | Hamilton
"Roger L. Costello" wrote:
>
> Hi Folks,
>
> You are invited to participate in the collaborative development of a
> distributed registry technology.
>
> We have created a list (distributed-registry) for discussion of this
> topic. To subscribe to the list send an empty email to:
>
> distributed-registry-subscribe@yahoogroups.com
>
> Here is a description of the purpose of a distributed registry:
>
> A Web service registry provides information about what services do, and
> how they are used. Today's Web service registries (e.g., UDDI and ebXML)
> are implemented as centralized repositories. That is, all services store
> their service descriptions within a single, or a small number of
> registries. The purpose of this effort is to develop a concrete,
> implementable architecture for a highly distributed registry. The notion
> is that each Web service defines their own registry - comprised of the
> collection of documents that describes the service.
>
> We have created a Web page which
> - lists the design goals for a distributed registry, and
> - proposes an architecture
>
> Here's the URL to the Web page:
>
> http://www.xfront.com/dist-reg/distributed-registry.html
>
> We invite you to participate in the development of this technology.
> Thanks!
>
> Roger L. Costello and David B. Jacobs
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
begin:vcard
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@bah.com
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard
|
