Future of Web:More Processors+ more AJAX + more Web Services (flexibility Vs Security)

Since Asynchronous Javascript and XML (AJAX)  was introduced first time through xmlHttp Object in IE browers by microsoft. Since then Every browser and Website runs on AJAX not waiting for synchronous reply from the server before sending another request. Client got freedom to seen any number of request anytime without waiting for arrival of reply.
AJAX shifted Web development balance more towards web scripting languages like JavaScript and vbscript from Server centric world of Java/ASP/Servlet.
AJAX API have come into being like for about anything from Mapping API of google, Charting and UI provided by JQuery, and better UI through Adobe Flex API using Action script, ExtJS library.
Server centric world have more sifted towards interoperability of  Web services with WS-i ans JSR 21. For better utilisation of components written as web service can be consumed by any Java or .NET or COBOL or SAP or Oracle apps.
With web services defined by (WSDL) web services definition language And three components Service Broker, Service Requester, Service Provider interacting with Each other to Expose as web service not only comes interoperate but since all web service properties are in XML thus achieving portability to other platforms like Java web service can talk to .net web service passing property details in XML format.
Now if data fetched from databases in put into XML format. data Also become portable to and database ..like you can take data out from oracle in XML and import to SQL server and so on..
PHP not only was first to popularize AJAX but also first to introduce Restful web services.
now instead of SOAP request to server the client sends SOAP over http thus web service request is just like URL. This provided lot of flexibility and security. As Earlier firewalls were made to intercept http header request but not SOAP header request. There were things like Schema poisoning, SOAP injection etc.. But today’s firewalls can track these all to details we want.
So front end AJAX API revolution  and server side moving towards restful web services. This Flexibility in AJAX also raised lot of Security concerns like cross site scripting (XSS) attacks, injection of javascript , (CSRF) Cross site Request Forgery and cryptographic security at web server services like JAAS Java authentication and authorisation API, (JCA) java cryptography API, similarly  .NET  Also have similar API.

With in few year code sifted more from server side to client side with AJAX, Json etc So from 90:10 ratio to present 60:40 the movement has be relentless. But it have been marred with all security concerns of code present at client side.
Now we Even have server side javascript as well with Node.js.
with Flexible scripting languages like DOJO which provides so many options as compared with plain javascript. And Now we even talk reverse way by which javascript function can
Usually user request through JavaScript to server side JSP/ASP/Servlet.
But in reverse way also through Java Web R emoting : JavaScript can use methods implemented in Server side code directly. can can request for data. while server also tightly coupled with client can refresh client code any time like Cricket score websites.
server can refresh the client with new code same way client can request new data and client javascript can use java server side functions directly using JWR.
ore and More code will move towards client with AJAX to Server code ration if 40:60 it will go to 50: 50 to may be 60:40.. As the number of chips available on client machine motherboard continue to increase with i7 being 1 master chip and 6 slave chips (its like tree of level 3.  so 2^(3-1) = 7 CPU..
In future there might be 23 CPU in your system so we can execute more code in parallel
Read how this will effect programming: