[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Evaluating RPC versus REST
Which is why "impress me" is stronger than "imprimatur", IMO. Selling the imprimatur and demanding fealty for it sounds a lot more like enslavement than pay for the patent or negotiate or just build it and let's see what works. I am a believer in the rights of the inventor, sort of the Howard Roark approach. It didn't mean he wouldn't help; it meant he had the right to set the terms and the reasonable expectation these terms would be met. One does not serve on demand, but on request and acknowledgement. When we started calling specs for emerging technologies, "standards" we forged our own chains. When we demand global namespace as the only right way to build Internet applications, we forge our own chains. If we ignore an emerging tech or fail to recognize the utility of the namespace, we can dig our own latrines and might leave our businesses in them. Choice is risky. Live long and prosper, or live short and wither. But regardless, communication is about choice. My fear is that to be heros or to unify, we are forging chains. Our privacy is already gone. Will our choices go next? paranoidly yours, len From: Mike Champion [mailto:mc@x...] I just want to make sure that a decision to standardize on the RPC paradigm today doesn't lose us a war with the aliens in 2150, as all those threads waiting for a response to an RPC invocation of a web service light-minutes away lock up the command and control systems <grin>.
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|