On 11/01/2008, Alexander Johannesen <[EMAIL PROTECTED]> wrote: > > > > > > > Hi Gregg, > > I wrote: > > > GET > > > http://example.com/some_service/resource?transactionID=xxx&leaseID=yyy > > Gregg Wonderly <[EMAIL PROTECTED]> wrote: > > The use of those parameters in the URI is a proprietary type of solution. > > The implementation certainly is, but the interface is not. But this > was just an example. I don't know Jini or Jiri, but I'm sure there's > ways to RESTify their semantics.
The interface is proprietary as its specific to a given implementation, linked directly to that implementation and not managed by any sort of standards body. MQSeries uses TCP/IP that doesn't mean that MQSeries interfaces aren't proprietary. > > > It works for that service because I know how to use that service. > > Which isn't different to "Jini 'services' works because you know how > to use Jini." It is as I can download a formal specification for Jini, build my own implementation and have all the proxy/dynamic code/lookup/leasing/etc stuff work and interoperate with others. REST provides a syntax but not the semantics.
