On Jul 11, 2006, at 5:54 PM, Dan Creswell wrote: > And as it appears that's what you'd have to do many people are > wondering > how that's much better than defining it all on some contract/interface > be it implemented via RPC or some other mechanism.
Because there will be integration at some point and with e.g. RPC you have to deal with: - the behavioural contract - the API - the data with REST you only need to consider - the data IMHO it is much easier to *only* having to translate between different data representations of state than it is to translate between different behavioural and API contracts *and* the data. Jan ------------------------ Yahoo! Groups Sponsor --------------------~--> Something is new at Yahoo! Groups. Check out the enhanced email design. http://us.click.yahoo.com/SISQkA/gOaOAA/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/
