[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Demand for web services

• To: jim.fuller@r...
• Subject: Re: Demand for web services
• From: Anne Thomas Manes <atmanes@g...>
• Date: Mon, 1 Aug 2005 08:37:28 -0400
• Cc: Michael Kay <mike@s...>, joe@r..., xml-dev@l...
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=k3oITJKOOiXKq0P7p2edQmmEsx9T8JKMtV7mgOqIET1XFaSkaHdYADK7zWBFYM7d1iNsjKE3v31uM4WXDfnEOjsd3YRbfdRL+B6wCHCPKSQAIqp1k3AvuzH1qTgMUhaOc68TFvPgf9BeH5+/LYstiLRIfAHglvO+n9Htjg3ILu0=
• In-reply-to: <42EE0E5E.7020401@r...>
• References: <200508011105.j71B5HL00499@s...> <42EE0E5E.7020401@r...>
• Reply-to: Anne Thomas Manes <atmanes@g...>

I'm with Jim. The primary driver behind (first) XML-RPC and (second)
SOAP-based web services was originally and continues to be the need to
make heterogeneous systems interoperate. It's about separation of
concerns at the middleware level (platform/language/infrastructure),
not at the presentation level.

Anne

On 8/1/05, James Fuller <jim.fuller@r...> wrote:
> Michael Kay wrote:
> 
> >I think web services were driven more by the need to deliver XML data to
> >applications that carry out business logic using the data, rather than
> >merely doing presentation. People who only want to do presentation have
> >largely found that HTTP is sufficient. But that's just one view...
> >
> >
> +1 to this view,
> 
> I would think that the primary use case *currently* for web services
> adoption is dealing with enterprise level integration where there are
> plenty of suppliers with plenty of heterogeneous systems and
> software...all set within a more closed 'extranet' type environment.
> They are not being driven at the 'web' layer where 80% of us live,
> though things such as REST are growing up from the grassroots and things
> such as WS* are growing down, hopefully they will meet up.
> 
> the next primary selection characteristics for web services (for the
> future) would be;
> 
> - perform software to software integration, underpinning true machine to
> machine collaboration (e.g. along with commodisation it brings)
> 
> - application composition enabled using real time service discovery and
> inspection
> 
> as for seperation of content and presentation...not sure if perhaps its
> confusing to use the term presentation where 'interface' would do, along
> with 'content' where 'data' would....slight differences in semantics
> though implying that a human is involved in one whereas it is not in the
> other.
> 
> cheers, Jim Fuller
> 
> -----------------------------------------------------------------
> 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://www.oasis-open.org/mlmanage/index.php>
> 
>

• References:
  • Re: Demand for web services
    • From: James Fuller <jim.fuller@r...>

• Prev by Date: Re: Demand for web services
• Next by Date: RE: Demand for web services
• Previous by thread: Re: Demand for web services
• Next by thread: RE: Demand for web services
• Index(es):
  • Date
  • Thread