On 7/7/06, Dan Creswell <[EMAIL PROTECTED]> wrote: > Mark Baker wrote: > > On 7/6/06, Steve Jones <[EMAIL PROTECTED]> wrote: > >> Now either I've been incredibly lucky or I only build mickey mouse > >> apps... but I've never had this problem. > > > > Another possibility is that you don't realize how simple things can > > really be? That's how it was for me, at least. > > > >> What form of scalability are you refering to? > > > > Number of services. With Web services, for each new service that's > > added to the system, in order for existing components to be able to > > communicate with it, you have to modify them (ignoring the data issue, > > which is the same with both). Not so with REST. > > > > Oh, err, not with you - if we are ignoring the data issue what other > modifications are we talking about?
If I have an existing client that retrieves real time stock quotes via a getRealTimeStockQuote operation on a service, and I later add a delayed stock service which offers its data via getDelayedStockQuote, then in order for that same client to get the new data, it needs to be updated to use that new operation. But if both the client and the two quote services had used a more general operation, like getStockQuote() (or just get()/GET), then no modifications would be necessary to the client. Of course, we're assuming a standardized stock quote data format is used in both cases. Mark. ------------------------ Yahoo! Groups Sponsor --------------------~--> Great things are happening at Yahoo! Groups. See the new email design. http://us.click.yahoo.com/TISQkA/hOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
