Computer at one end, computer at another, integration being done by one piece of code at one end talking to the other piece at the other end. Is the Systems bit.
The Integration bit (for me) is the logical integration of an external application/service/resource into the logic of the local application/service/resource in otherwords its a SEMANTIC integration (behaviour and data) rather than just being an information exchange. FTP for instance isn't on its own integration, its only integration when something is done with a known purpose and when it delivers a known result. Dull old B2B integration in fact. Having a person acting as the integration or semantic agent doesn't (for me) cut it. Steve 2008/11/10 Jan Algermissen <[EMAIL PROTECTED]>: > > On Monday, November 10, 2008, at 10:31AM, "Steve Jones" > <[EMAIL PROTECTED]> wrote: >> >>But back in 1991 it wasn't RESTful and was still possible. Its a >>brilliantly simple (IMO the best inventions are) mechanism for >>inter-document linking, that superbly took the complex SGML and >>concepts from Hypercard and its ilk and delivered in a massive >>distributed way a simple solution. Its document linking rather than >>systems integration however. > > Steve, > > could you clarify what it means for something to be 'systems integration'? > What are the properties of a technology/approach that make it a systems > integrations technology or approach? > > Jan > >> >> >>> >>>> Just a quick question: Are you saying that HTTP and the href tag is >>>> sufficent for a site to claim it is doing REST style integration? >>>> This way it would be the case that sites that just use POST for >>>> everything would be fully REST compliant. >>> >>> No. >> >>Thank god for that, I was about to have to re-write a presentation on REST >> ;) >> >>Steve >> >> >> >>> >>> Mark. >>> >> >>------------------------------------ >> >>Yahoo! Groups Links >> >> >> >> >> >
