Jan Algermissen wrote: > > ------------------------------------------------------------ > Jan Algermissen > http://jalgermissen.com > Software Architect > http://www.tugboat.de > > > > On Friday, January 19, 2007, at 09:04AM, "Gregg Wonderly" <[EMAIL PROTECTED]> > wrote: >> Jan Algermissen wrote: >>> The difference is that HTTP is an application interface. It is the >>> interface of the user's application. >> RMI/JERI is an application interface. The application uses this paradigm >> for >> remote data transfer via the parameters of the "invoke" operation. > > So you'd never put another layer of semantics on top of that then? What does > invoke mean? > >>> When you buy a book at Amazon, the application interface you are using >>> is HTTP. >> The application's interface is exported as an HTTP endpoint. > > No, HTTP is the application interface semantics. There is no application that > is mapped or whatever to HTTP (set aside any backend stuff of course). > > Is this really impossible to get across? >
I guess it is because I think the application's interface is the browser..... > Jan > > >> Gregg Wonderly >> >> >> >> Yahoo! Groups Links >> >> >> >> >> > > > > Yahoo! Groups Links > > > >
