Re: [service-orientated-architecture] RESTful lightbulb

Fri, 07 Jul 2006 08:28:29 -0700

But Mark that was my point. In order to really save time and decrease complexity you need to agree on the data. If there is no agreement then integration of my editor is about of the same complexity in both cases regardless of your logarithms ;-)

And, btw, the fact that APP and GData are on the Web proves there is a further need for simplification beyond REST academia.

On 7/7/06, Mark Baker <[EMAIL PROTECTED]> wrote:

Hey Radovan,



On 7/7/06, Radovan Janecek <[EMAIL PROTECTED]> wrote:
>
>
> So let's imagine I want to create new web site that will provide blog editing functionality and I will want to integrate with existing blogging systems. All of them provide HTTP access to insert new posts, comments, and so on. Users of my site will edit new posts in my editor and publish them on their blog servers.
>
> So beside writing the superb editor I have the integration task. Can you explain how much easier this task is with REST than with WSDL? All I see is that if I want to support one more blog server ('the new service added to the system') I just need to write new integratoin code into my editor. In both cases.

Not if all the blogging systems support the same interface & data
formats, right? Then you just need to "point" your already developed
code at the new system.


> If there was strict payload agreement then, of course, the integration would be easy. I'm sure APP will solve this for one domain. Some GData-like solution for another domain. We are not there yet on the Web and certainly not in enterprise.

So what domain can't you use APP (or GData, which is based on APP) for?

BTW, both APP and GData are on the Web.

Mark.




--
Radovan Janecek
http://radovanjanecek.net/blog __._,_.___


SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture

YAHOO! GROUPS LINKS



__,_._,___

Reply via email to