Problem Statement : perl server side templating tool kits.

opportunity a : understanding from the above ...a innovative XML-CSS ...client side templating toolkit for GUI rendering

              embeddedable and usable as a wiki-widget toolkits for GUI-OS.

              refer to the document "opportunity_GUI_wikitool_kit_mobile_OS_applications.txt" and various other envisaged
              use-case scenarios "opportunity_packaging_innovative_non_native_fonts_on_OS.txt"


              also evaluating the scope of such a programming context from the point of  XML-RPC and web x.0 technologies
              when interacting with server-side,

Opportunity b : deriving from above ...a innovative client side ...template's[re-defining...some components used in two tier technologies
              and RAD] that can glue-in or gell with DBI/DBD /other similar  comparable technologies , interfaces on the server-side

              using xml-rss-rpc / webx.0     

Opportunity c: with lot of server-side content management and layout   engines ...around

                     ...repackage the same as a client-side ...java-jar/zip/remoting-cab....with self-synchronization of
                     the jar/cab/zip with update available  from time to time on the server-side.  

              using XML-RSS or http-meta-tag[refer else-where as envisaged by this individual with reference to content caching and expiry]
              based content update or synchronization in templates with server-side.


Opportunity d: understanding and interpreting from Ajax ....

               deriving from opportunity a,b,c) as above as also ability to use the traditional server-side pre-processor engine's[cfml/php/perl-templates]
               on the client-side....based on the specific platform packagable as a java-jvm or activex or perl-engine ...[argubly .NET] ...ETC


Opportunity e: deriving from opportunity a,b,c,d ...usage of and exploiting DHTML in combination
               with XML-[dom] content streaming for lite weight ...client-side pre-processor based content and layout driven engine's.
               Thus XML-DOM parsable data-source from which to retrive data and writing (java-script) the data into DHTML engine driven
               content-layout into the elements of DHTML documents. 

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.

             


                               