2 ms·
> I don't see any reason why SOAP can't support dynamically changing sets of procedure calls. Furthermore, I think that is a bad idea since it will break backwa
by noblethrasher 15y ago
> I don't see any reason why SOAP can't support dynamically changing sets of procedure calls. Furthermore, I think that is a bad idea since it will break backward compatibility. No amount of web-buzzwording will get around that problem.
Of course enclosing a message in a SOAP envelope does not preclude RESTfulness. If the set of messages to which an object responds is a function of its current state then it's RESTful (or at least lead to a RESTful design).
- javascriptlol 15y agoSo what you're admitting is that REST doesn't add any new novelties in terms of being discoverable?
- noblethrasher 15y agoREST doesn't offer new novelties because the basic idea is at least as old as Smalltalk. REST isn't even about discoverability. That's just a natural consequence of calling methods that might only exists when an object is in a particular state (i.e. the object creates the methods at runtime). The difference between REST and (usual) SOAP is the difference between late-binding and "extreme late-binding"[1] [1] http://www.google.com/#sclient=psy-ab&hl=en&source=hp&q=%22extreme+late+binding%22&pbx=1&oq=%22extreme+late+binding%22&aq=f&aqi=g-v1&aql=&gs_sm=e&gs_upl=841l7001l0l7239l22l22l0l0l0l0l170l1916l16.6l22l0&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=32d11c21ee39213c&biw=1066&bih=610 http://www.google.com/#sclient=psy-ab&hl=en&source=h...