Or to put it another way Java and .NET developers like clearly defined elements as they know that this reduces support costs. PHP and Ruby developers are concentrating just on the development part so don't consider the long term....
:) Fast should be about the lifetime, not about the first go live. Steve On 28/03/2008, Scott C. Sanchez <[EMAIL PROTECTED]> wrote: > > I've noticed that when I talk to developers, Java and .NET developers > prefer to consume SOAP (wsdl-based) services that they can easily import > into their IDE, where as PHP and Ruby developers prefer to consume > REST-based services since they are simple and fast, much like their choice > of language. > > -Scott > > > > > On Fri, Mar 28, 2008 at 10:23 AM, Anne Thomas Manes <[EMAIL PROTECTED]> > wrote: > > > On Wed, Mar 26, 2008 at 3:44 PM, Michael Poulin <[EMAIL > > PROTECTED]<m3poulin%40yahoo.com>> > > wrote: > > > > > > One of lead architects around me said that SOA and RIA are almost > > orthogonal > > > because RIA demands fine-grained operations while SOA tends to > > > coarse-grained ones... > > > > > > - Michael > > > > Hence my assertion that RIA and mashups will become more intimately > > connected with SOA if/when > > REST becomes a predominant approach for building services. > > > > REST exposes capabilities through a resource interface. (see my recent > > post, REST is about Resources > > [http://apsblog.burtongroup.com/2008/03/rest-is-about-r.html]). The > > resource interface is fine-grained. Any "thing" that you want to > > interact with has a URL. RESTful services are significantly easier to > > interact with than SOAP APIs, particularly from the RIA and mashup > > tooling perspective. > > > > (Note that the RESTful service can still be coarse-grained -- but the > > interface [the resources it exposes] is fine-grained.) > > > > Anne > > > > > > > > > > > ----- Original Message ---- > > > From: Rob Eamon <[EMAIL PROTECTED] <reamon%40cableone.net>> > > > To: > > > [email protected]<service-orientated-architecture%40yahoogroups.com> > > > Sent: Tuesday, March 25, 2008 2:37:30 PM > > > Subject: [service-orientated-architecture] Re: Meehan on RIA meets SOA > > > > > > > > > > > > > > > Why is that? Why would an RIA be "more connected" to services based on > > > the interaction style? Why would accessing services via REST vs. any > > > other mechanism be considered more connected? A service consumer is a > > > service consumer, regardless of the service interface, no? > > > > > > Or are you referring to the relative prevalence of an RIA's use of > > > services compared to other approaches? > > > > > > -Rob > > > > > > --- In service-orientated- architecture@ yahoogroups. com, "Anne > > Thomas > > > Manes" <[EMAIL PROTECTED] > wrote: > > > > > > > > RIA and mashups will become more intimately connected with SOA > > > > if/when REST becomes a predominant approach for building services. > > > > > > > > Anne > > > > > > > > > > > > ________________________________ > > > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try > > it > > > now. > > > > > > -- > > ------------------------------------------------------------------------- > This message contains confidential information and is intended only for > the intended recipient(s). If you are not the named recipient you should not > read, distribute or copy this e-mail. Please notify the sender immediately > via e-mail if you have received this e-mail by mistake; then, delete this > e-mail from your system. > > >
