Linked by mufasa on Mon 10th Aug 2009 12:25 UTC
Web 2.0 The web browser has been the dominant thin client, now rich client, for almost two decades, but can it compete with a new thin client that makes better technical choices and avoids the glacial standards process? I don't think so, as the current web technology stack of HTML/Javascript/Flash has accumulated so many bad decisions over the years that it's ripe for a clean sheet redesign to wipe it out.
Permalink for comment 377960
To read all comments associated with this story, please click here.
Member since:

XML-RPC makes sense sense for web services because a) it goes over port 80, which means less firewall headaches, and b) it is xml, which is designed to be parsable by anyone (including humans)

JSON makes sense because XML is incredibly verbose, and if you are communicating back and forth with javascript anyways you may as well be using its native object notation anyways. It still uses text, again, because you want it to work with web servers.

Binary RPC calls make sense when you control both the client and the server, and performance outweighs interoperability.

Reply Parent Score: 4