On 11/12/06, Alexander Johannesen <[EMAIL PROTECTED]> wrote: > > > > > > > On 12/12/06, Andrew S. Townley <[EMAIL PROTECTED]> wrote: > > [good stuff] > > Thanks Andrew for that mail, good stuff! And thanks Jan; you're both > very, very patient. :) > > I think it's important to note how much REST actually is like the Web > itself; it's not about RPC as in you've got this big API and you need > to know a lot of shit to know what part of it to use at what time. > Throw all of that out, and let REST give you *exactly* what you can do > at that perticular time, and just trust the expert (the service). > is no different from well-designed web applications where user > interaction in the user interface defines "what to do next." > > REST is interactive, keeps its own state and limits the API to that > context, while WS-* is just another RPC stack where you keep your own > state and you must know bucketloads on how that state impacts with the > fullness of the API.
Alex, PLEASE go an read more on WS-*, most people aren't using it as RPC _between_ endpoints, but are providing an "object" style interface onto the invocation sides of the exchange, thus hiding the complexity from the developer. You also _don't_ have to know "bucketloads" on how that state impacts things if the service has been well designed, you need to know _enough_ to complete your interaction. REST also requires you to understand the impact of state change. > > Alex > -- > "Ultimately, all things are known because you want to believe you know." > - Frank Herbert > __ http://shelter.nu/ __________________________________________________ >
