problem statement: DNS round robin scheduling is used as kind of loadbalancing mechanism
                    in crude sense.


opportunity :  A innovative means of implementing loadbalancing in software requesting
               routing and servicing is

               implement a hash of weighted averages of all the software hosts or systems involved
                based on various parameters considerable ...viz. no of processors, memory,etc

               at router level implement a NAT(takes care of or into account the session management)
                algorithm that does a request routing based on the
               the weighted average's and request counter kept in the hash for the purpose.


               [while it may be noted that session management param's encoded into url may resolve the
                nunances to a great extent but as the number of tier's or level's say NAT,DNS,load balanced databases
                or distributed databases ....the complexities can complicate and difficult to negotiate if not aptly be
                tackled]


                while ideally grid-computing isn't a special case in itself ....use-case modeling maybe applied , 
                for certiain circumstances where internal communication channel's like back-pane are involved!!.


Note: The above problem statement having been encountered in various scenarios
      and detailed in various 'Proof of concepts' as mentioned in 
      
       http://uk.geocities.com/ravivenkatus/projects.pdf
       http://ravishankarkv.tripod.com/projects.pdf
        ....apply appropriate
      'use-case' modeling, rationalize and arrive at a workable and feasible 
       solution both commercially and techinically viable.


   
   
