W3C home > Mailing lists > Public > www-ws-arch@w3.org > January 2003

Re: Issue 5 and "webarch"

From: Walden Mathews <waldenm@optonline.net>
Date: Sun, 05 Jan 2003 23:09:26 -0500
To: "Champion, Mike" <Mike.Champion@SoftwareAG-USA.com>, www-ws-arch@w3.org
Message-id: <005c01c2b539$6719c2a0$1702a8c0@WorkGroup>

> Let's say that the T-Rex accounting system has to access this invoice
(which
> let's assume is physically on another mainframe Bronto at a remote site.
> Mark seems to be suggesting that it dereference
> http://bronto.example.com/9238d928jd298sdfi9 and get the data.

Does he really?  That would surprise me because although these mainframes
may be separated by a network, it doesn't sound from anything you've said
that they would be loosely coupled or managed by people who don't trust
each other.

 >That assumes
> that the accounting system (first deployed in 1975, let's say) understands
> HTTP, and is connected to the internet (which for some odd reason
mainframe
> sysadmins tend to be paranoid about).

It doesn't assume that, but it's moot, see above.

 >In the current world, let's say that
> T-Rex communicates with Bronto via a proprietary MOM (that provides
> reliabile messaging, security,etc.), and 249827348237432 is the primary
key
> of the invoice of interest in some database.  In this type of scenario, it
> makes a lot more sense for the SOAP client to gather up all the data that
> the back-end system needs, pass it through the HTTP/SOAP gateway, and let
> the back end do what it was built to do, than to rebuild all that back
> office stuff with Web technology and model the interactions with
hypermedia.

Why would you need a SOAP client here?  Check this out: "it makes a lot more
sense for the client program to gather up all the data that the back-end
system
needs, pass it through the MOM infrastructure, and let the back end do what
it
was built to do, than to rebuild all that back office stuff with SOAP
technology
and model the interactions with XML."  Sounds good?

>
> I'm suggesting (well, insisting!) that the Web services architecture
reflect
> this reality as well as the scenario in which all these exchanges are done
> with HTTP over the Web per se.

How does the name "Services Architecture" strike you?  Sounds like something
that's already been done, huh?

Walden
Received on Sunday, 5 January 2003 23:09:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:12 GMT