Problem Statement: Further to as published or illustrated in the document referred
                   below viz. projects.pdf  and elsewhere as published and envisaged by this individual.

Opportunity a): number of descriptors that can be  handled  by  a process or a process-stack??

                   given that  the software or stack of applications that comprise a Operating system 
                   can be classified or differentiated based on the principles of atomicity and division of labor
                   viz. the intended purpose or usage of the application ....thus arising the requirement of
                   each of these stack of application or os-layers and their requirements vary.

                   thus ability to treat a descriptor as base-class in the programmatic-context, derive and the ability
                  ability to control various features ,intended  purpose as also number of instances ....thus the ability
                  to control the amount of flexibility to a programmer or developer when writing or developing custom
                  interfaces and code to various stack of applications and their intended usage.  

                 While the idea the objective as above ...which is relatively easy to envisage and implement
                 in OOP lanuages ...but drawback being also resulting large footprint for the binaries ...??,
                ...explore the scope and idea or retaining the OO thinking of the whole requirement ,ability 
                to achieve the same in 'C' or its equivalent programmatic interface's resulting efficient binary
                size ...the above may potentially be describable or equivalent to device and its handler a file-descriptor
                in unix-parlance (a array of unix header files and constants ...enums ...)

                ...from the eg scenario as envisaged in "opportunity_webapplication_performance_tuning.txt" , ability to
                handle the  same at the unix-device-driver level. 


Opportunity b): deriving and interpreting from how a 'env' ...configuration is accessed in certained operating environments

                ....for a programmatic interface ....ability to query list of available standard descriptors

                (gigabit/blootooth/network/scsi/iscsi/fibre/RF) from such an env would make a ideal proposition, a potential
                way to extend existing programmatic models is ....ability to map or bind a descriptor/descriptors to 0,1,2.


                java ...namespace ....jit offers a decent means of building binaries ...liet-weight ...also ability to
                configure or use such a namespace scope for library access would offer ideal proposition, rather than a 
                include ...programmer-reference's swelling the binaries.


                perl/python ...combination offers ideal proposition ...refer as envisaged else-where by this individual.


Opportunity c): further to as envisaged or scope ...defined

                  deriving from b) as above ....a understanding io-blocking ...device descriptor

                            ....a innovative programmatic model ...alogical or envisable on the lines of posix threads,,,


                             ...a universal device neutral ..and protocol neutral or a programmtic model that shields
                             the programmer from nitti gritties of the nuiances of device and protocol ....

                             to be able to fiddle with such devices ...ideall mapping to the standard descriptor 1,
                             may require changes as or changing in handling the interface when dealing with two-way communication...

                             or deriving if all input were to be written to 0 ...or recieved on 1 and error handling on2!!.

        loose ...illustrative...envisaged...programmatic model

         while( 1 ){

                    if( cin || cout){


                    }

                    elseif(cout || cin){

                    }
                    elif
                    {
                       cout<<2>>hesheheshe .....

                    }

        }
                

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.