OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: [xml-dev] Exposing resources/services vs hiding implementation detai

[ Lists Home | Date Index | Thread Index ]
  • To: "Michael Champion" <michaelc.champion@gmail.com>,"xml-dev" <xml-dev@lists.xml.org>
  • Subject: RE: [xml-dev] Exposing resources/services vs hiding implementation details
  • From: "Dare Obasanjo" <dareo@microsoft.com>
  • Date: Tue, 5 Apr 2005 17:44:31 -0700
  • Thread-index: AcU6PAnCzln8LfVnRR2NY9rIvYRfEgABXO+A
  • Thread-topic: [xml-dev] Exposing resources/services vs hiding implementation details

> -----Original Message-----
> From: Michael Champion [mailto:michaelc.champion@gmail.com] 
> Sent: Tuesday, April 05, 2005 4:52 PM
> To: xml-dev
> Subject: Re: [xml-dev] Exposing resources/services vs hiding 
> implementation details
> 
> 
> My motivation in all this uber-permathread is that I opposed 
> the notion that was popular 3-4 years ago of extending the 
> COM/CORBA/RMI
> distributed object paradigm to the Web;    I agreed with the
> RESTifarians that it wouldn't scale, wouldn't leverage the 
> Web infrastructure, all the classic arguments that appear to 
> have been validated by Amazon, Bloglines, Flickr, etc.  But 
> now I'm questioning the currently popular notion that the Web 
> architectural style is generally suitable for enterprise 
> scenarios where COM/RMI/J2EE/etc.
> are entrenched.  

Interesting. Who's stated this opinion recently? 


--
PITHY WORDS OF WISDOM 
We make our friends. We make our enemies. God makes our next door
neighbor.    

This posting is provided "AS IS" with no warranties, and confers no
rights.  




 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS