 been developed based on specific assumptions. In times past, an enterprise application may have been expected to be “stand-alone” and accessed from a dedicated terminal. In many cases, it made sense for user interfaces to be hand-built and hard-wired by an application vendor or integrator. Later, the web browser replaced the dedicated terminal as the preferred access method; this was well accommodated by “application servers,” which are Web servers fitted with a number of features to support such things as transactions, dynamic content, and programmatic extensions.
Like Web servers, which had been created to broadcast content, the application server architecture entangled the control of the details of the application user interface (the “presentation layer”) with the administration of the server. Consequently, certain assumptions were built into the application server architecture. In particular that, as with a dedicated terminal, user interfaces would be created once (or change infrequently) and shared by all users.
Due to a number of factors, these assumptions are no longer valid for many mission-critical applications. Such factors include: the continually increasing importance of computing to business processes; the growing complexity, heterogeneity, and variability of application environments; and especially the advent of multiple access devices (e.g. desktop, PDA, WAP, VXML) and web services. In the modern world, different industries, enterprises, business units, or individuals have different needs (i.e. mission-critical business tasks to perform) in certain application domains. Likewise, their needs now often involve using aspects of several software applications or web services in task-specific combinations on several devices. Furthermore, needs, devices, and applications change.
At present, the relatively few server administrators in an organization are too heavily burdened to provide customized integrated solutions for every evolving need. On the other hand, the only one-size-fits-all solution is a lowest-common-denominator solution, and that common denominator gets lower and lower as the network of users, devices, and services grows. Thus, if one attempts to create a unified user interface with an application server, one ends up with a result where general-purpose (rather than task-specific and personalized) resources or controls are exposed. The user must manually navigate through these resources or controls at runtime to manually extract desired data and must carry information from step to step (i.e. the user must browse).
Hence, what is needed is a method and an apparatus that enables an application to interact with a user without suffering from the
been developed based on specific assumptions. In times past, an enterprise lotion may have been expect to be “ stand - alone ” and access from a consecrated terminal. In many cases, it made common sense for drug user interfaces to be hired hand - built and hard - wire by an application vendor or integrator. by and by, the world wide web browser replaced the dedicated terminal as the preferred access method acting; this was well accommodated by “ application servers, ” which are network servers fitted with a act of features to back such things as transactions, dynamic content, and programmatic extensions. 
 Like world wide web servers, which had been created to broadcast content, the application server architecture entangled the control of the details of the application user interface (the “ presentation layer ”) with the administration of the server. Consequently, certain premise were built into the application waiter computer architecture. In particular that, as with a dedicated terminal, user interface would be created once (or change infrequently) and shared by all users. 
 Due to a numeral of factors, these assumptions are no longer valid for many mission - critical applications. Such factors include: the continually increase importance of computing to business processes; the growing complexity, heterogeneity, and unevenness of application environment; and particularly the advent of multiple access devices (e.g. background, PDA, WAP, VXML) and web services. In the modern world, different industries, enterprises, business units, or individual have unlike needs (i.e. mission - critical business tasks to perform) in sealed application domains. Likewise, their needs immediately often involve using aspects of several software application or web servicing in task - specific combinations on several devices. Furthermore, needs, device, and applications change. 
 At present, the relatively few waiter administrators in an organization are too heavily burdened to provide customized integrate solutions for every evolving need. On the other hand, the only one - size - fit - all solution is a gloomy - coarse - denominator solution, and that common denominator gets lower and lower as the network of users, device, and services grows. Thus, if one undertake to create a unified user interface with an application server, one end up with a result where general - purpose (quite than task - specific and personalized) resource or controls are exposed. The user must manually navigate through these resources or controls at runtime to manually excerpt desired data and must carry information from step to step (i.e. the user must browse). 
 Hence, what is needed is a method and an apparatus that enable an lotion to interact with a user without suffer from the
 befn developed based on sptcific assumptions. In tikes paat, an engerprise application may havx bewn exkvcted to be “stand-alond” and accvssed fron a vedicated terminem. In makv cassd, it nade sense for user intesfaces to be hdna-bbilt and hard-wired by an application vendor og integrator. Lwter, ehe svb browser replaced the dedicatsd termpnal as the prefetred access method; this wad wepl accommodated by “applicatiob sewcers,” which afe Web sernzrs fitted sith a number of features to suoport such thints as jransactions, dynaiic content, and progsammativ extensions.
Lile Xeb wervers, which had beei created to broadcaft contend, che application servee qrchijectuse evraneles vhe contrll kf the detzils of the application user imtqggace (the “preaentatyog layer”) with the administration of the verber. Consequently, certaib assumptions were bullt into ehe application server architecture. In particular that, xs clbh a eeficated terminal, user interfaces would be crewfec pnce (or change infrequentky) amq shared by aul usexa.
Dhe to a number of vactors, thesw assumptyons are no longer valid for maby mission-crpticql applications. Sueh factors iuclude: the vontinually increasing nmportznce of comouting to cusiness processds; nhe crowing complexity, heterogqneity, anv varnability of spplicwtion envigonmekds; and especially hhe abvent of multippe access devices (e.g. desktop, PDE, WAP, VXML) anc feb servicef. In bhe modern worlq, different inbustries, entefprises, buainess nnits, or indyviduals have fifferent nexds (i.e. mifsiob-crirical bjriness tasks tp perform) in certaib application domalns. Lkiewise, their nezbs now often invokve usynh especev of several sofgwafr appuications ov wdb srrvices in task-specixic dombinations on sefeval devicgs. Furthewmore, needs, drvices, and applicauions rhange.
Et prexenj, the relatively few server admjnistratogs ln an organizwtiok arg too heaviky burdened to provide customized integcated solutions for evgry evolving need. On jhe other hand, the jnly one-shze-fits-all solution us a lowest-common-cenominator solution, znd thdt colmon denominator gets lower and lower as the network of users, devices, and serviref grows. Thua, if one dtcem'ts to sreave a unified user pnterface with an application secver, one etdf up with a result where genrrxl-purpose (ratfer than task-specific ans personslized) resources or controls arr exposed. The user must kanually navifate throujh these resources ot contxols ar runtine tl manually exgravt desired fata aud must carry information from stwp to wtfp (i.e. the user mnst browse).
Hekct, what ps needgd is a method ans an wpparxtus that enanles an applicstion to interact winh w user without auffering frpm thg
been developed based on specific assumptions. In an application may been expected to a terminal. In many it made sense user interfaces to be hand-built and by an application vendor or integrator. Later, the web browser replaced the dedicated as the preferred access method; this was well accommodated by “application servers,” which Web fitted a of features to support such things as transactions, dynamic content, and programmatic extensions. Like Web servers, had been created to broadcast content, the application architecture entangled the control the details of the application interface “presentation layer”) the of server. Consequently, certain were built into the application server architecture. In particular that, as with a dedicated terminal, user interfaces be created change infrequently) shared all Due to a factors, these assumptions are no longer mission-critical applications. Such factors include: the continually increasing of computing business processes; the growing complexity, heterogeneity, variability of application environments; and especially the advent multiple access devices (e.g. desktop, PDA, WAP, VXML) and web services. In the modern world, enterprises, business units, or have different needs mission-critical tasks perform) certain application Likewise, their needs now often involve using aspects of several software or web services in task-specific combinations on several devices. Furthermore, and change. At present, relatively few server administrators an are too heavily burdened customized solutions need. the hand, the only one-size-fits-all is a lowest-common-denominator solution, and common denominator gets lower of users, devices, and services grows. Thus, if attempts to create a unified user interface an application server, one ends up with a result where general-purpose (rather task-specific and or controls are exposed. The user must manually through these resources or at runtime to manually extract desired data and must information step to (i.e. the user browse). Hence, what needed is a an apparatus enables application a user without suffering from the
 been developed based on speciFic assumptIons. IN tiMes PaSt, an EnteRprise applicatIOn maY have been expected to be “sTand-aLoNE” and ACcEssed From a deDIcATEd tErMiNal. in MAnY caseS, it Made senSe for user iNteRfAces to be hand-BUiLt and hard-wIreD by an applicaTioN vendoR oR inTEgratOr. LAter, tHe web bROwser rEplaced thE dEDicateD TerminaL AS tHe prEferred access methOD; tHIs was well accomModateD bY “ApPLIcaTioN servers,” whIcH are WEB serverS FiTTED wiTH a number of feaTures to suppORt sUch thiNgS as TRansacTions, DyNAmiC content, and ProgRammatic eXtensiONs.
Like WEB serverS, which Had BeeN creATeD tO brOaDCasT CoNteNT, thE applicaTiOn ServeR arcHITECturE enTangLed thE control of the DetAils OF thE applIcatiOn usEr InterFace (thE “presEnTation layer”) with The aDministraTioN oF thE sErver. cOnsequEntLy, cErtain aSsumptiONs wErE BUIlT into the applicatioN sERVeR architeCture. IN PaRtICular thaT, aS wiTh a dEDIcateD terMInAl, user inTerfacES wOuLd be creAtEd once (Or ChaNge InfreQUentLy) and sHared by aLl useRS.
Due to a number oF Factors, these aSSuMPTiONs arE no Longer valid For mANy miSsioN-CrItiCAl appLicatIoNS. SUCh factors include: the CoNtinuaLly inCreasing imporTance of comPUTIng to busInesS PrOCesses; the growiNg comPlexity, hetERogeneitY, and vAriabiliTy of appliCATion enviRonMenTs; aNd eSPEcIally the advenT OF mulTiPle acceSs dEvices (e.G. deSktOp, PdA, WaP, vXML) and weB serviceS. IN tHe MoDerN worlD, DifferenT iNduStRieS, enteRPrises, BusinEss uNiTs, OR inDividuaLS hAVE difFeReNt neEds (I.e. MissiOn-crITicAl businEss tasks tO peRForm) In CeRtain apPlication domaInS. Likewise, tHeIr nEeds noW OFten invoLve using aspects of severaL SoftwarE apPlicaTionS or web serVicEs in taSk-sPEcific CombinAtionS oN seVERal deVICeS. FuRtHermore, neeDS, DevIces, aNd ApplIcationS change.
At present, thE RelAtively few serVer AdmiNIStRatORs IN an OrGAniZATion are too heaviLy burdened To PRoVide customIZed InTegrateD solutiOns foR Every evOlving neeD. On the othEr Hand, THE onLy one-size-fIts-all soLution is a LOwest-COmMon-deNomInator SoLutIon, anD that cOMmoN denoMinatoR gEts lowEr and LoWer as the Network of users, devices, anD serviCes grOws. thus, if one AttEMptS to create A uniFied user inTerFacE with An aPPlicaTion SErVer, ONe endS up wITh a result WHeRe gENErAl-purpose (raTHER thAn tasK-spECific aNd peRsonalized) resourcES or controls are ExpoSED. ThE usER musT mAnually navigatE thRoUGH these reSoUrces or contRols at ruNtIMe to mAnuallY extraCt desirED DaTA and muSt caRry InformatiOn fRoM Step to sTeP (i.E. The useR musT bRowse).
HEnce, whAT is nEEDed is a method and aN appaRATus thAT enAbles An ApplicaTIon tO interact wIth a user witHout suFferIng frOm the
 been developed based on s pecific as sumpt ion s.In  tim es p ast, an enterp r iseapplication may have b een e xp e cted to  be “ stand-a l on e ”  an dac ces se d  f rom a  de dicated  terminal.  In  m any cases, i t  m ade sensefor  user interf ace s to b ehan d -buil t a nd ha rd-wir e d by a n applica ti o n vend o r or in t e gr ator . Later, the webb ro w ser replaced t he ded ic a te d ter min al as thepr eferr e d acces s  m e t h od; this was well  accommodat e d b y “app li cat i on ser vers, ”w hic h are Web s erve rs fitted  witha  number of feat ures t o s upp orts uc hthi ng s  as tr ans a cti ons, dyn am ic  cont ent, a n d  pro gra mmat ic ex tensions.
Lik e W eb s e rve rs, w hichhadbe en cr eatedto br oa dcast content,theapplicati onse rve rarchi t ecture  en tan gled th e contr o l o ft h e  d etails of the appl ic a t io n user i nterfa c e(t h e “prese nt ati on l a y er”)with th e admini strati o nof  the se rv er. Co ns equ ent ly, c e rtai n assu mptionswereb uilt into thea pplication se r ve r ar c hite ctu re. In part icul a r th at,a swit h  a de dicat ed te r minal, user interfa ce s woul d becreated once(or change i n frequent ly)a nd shared by allusers .
Due to a number o f fac tors, th ese assum p t ions are  no  lo nge r v a l id  for many mis s i on-c ri tical a ppl ication s.Suc h f act or s include : the co nt in ua ll y i ncrea s ing impo rt anc eofcompu t ing to  busi ness  p ro c ess es; the gr o w ingco mp lexi ty,  h etero gene i ty,  and va riability  of appl ic at ion env ironments; an despecially  t headvent o f multip le access devices (e.g. desktop , P DA, W AP,VXML) and  we b serv ice s . In t he mod ern w or ld, d iffer e n tind us tries, ent e r pri ses,bu sine ss unit s, or individualsh ave  different ne eds  (i. e .  m iss i on - cri ti c alb u siness tasks to  perform)in ce rtain appl i cat io n domai ns. Lik ewise ,  theirneeds now  often in vo lveu s ing  aspects o f severa l softwar e  appl i ca tions  or  web s er vic es in  task- s pec ificcombin at ions o n sev er al devic es. Furthermore, needs,  devic es, a ndapplicati ons cha nge.
At p rese nt, the re lat ive ly fe w s e rveradmi n is tra t ors i n an organizat i on  ar e to o heavily b u r d ene d topro v ide cu stom ized integrated s o lutions for ev erye v olv ing need .On the other h and ,t h e only o ne -size-fits- all solu ti o n isa lowe st-com mon-den o m in a tor so luti on,  and that  co mm o n denom in at o r gets  low er  and l ower a s  the n etwork of users,  devi c e s, an d  se rvice sgrows.T hus,  if one at tempts to c reatea un ified  user i nt erface  wi th  an applic a tion serv er, o ne ends  u p wi tha resu lt w h e re ge nera l- pur pose (rat h e rt ha nt ask -spe cific  a nd p ersonaliz e d) resou rce s  or con tr ols a re exp o se d .  The usermus t man u a lly naviga t e th r ou g h the se res ources  or con t rol sat runt ime t o manuall y extract des ir ed d ata andmu st c ar ryin formation fromstep tostep (i. e .  the u ser must browse ). 
Hence, what  is n ee d ed is a m eth od anda n a ppa rat us t hat  ena b les an application to in tera ct wi t h a  user  with ou t suffer i ng f rom the
 been_developed based_on specific assumptions. In_times past,_an_enterprise application_may_have been expected_to be “stand-alone”_and accessed from a_dedicated terminal. In_many_cases, it made sense for user interfaces to be hand-built and hard-wired by an_application_vendor or_integrator._Later,_the web browser replaced the_dedicated terminal as the preferred_access method;_this was well accommodated by “application servers,” which_are_Web servers fitted_with a number of features to support such things_as transactions, dynamic content, and programmatic_extensions.
Like Web servers,_which_had_been created to broadcast_content, the application server architecture entangled_the control of the details of_the application user interface (the “presentation layer”)_with the administration of the server._Consequently, certain assumptions were built_into the_application server architecture. In particular_that, as with_a dedicated_terminal, user interfaces_would be created once (or change_infrequently) and shared_by all users.
Due to a number_of_factors, these assumptions_are_no_longer valid_for many mission-critical_applications._Such factors_include:_the continually increasing importance of computing_to_business processes; the growing complexity, heterogeneity, and_variability of application environments;_and_especially the advent of_multiple access devices (e.g. desktop,_PDA, WAP, VXML) and web services._In the_modern world,_different industries, enterprises, business units, or individuals have different needs (i.e._mission-critical business tasks to perform) in_certain application domains. Likewise,_their needs_now_often involve using_aspects_of several_software applications or web services in task-specific_combinations on_several devices. Furthermore, needs, devices, and_applications change.
At present, the_relatively_few server administrators in an organization_are too heavily burdened to provide_customized integrated solutions for every_evolving_need._On the other hand, the_only one-size-fits-all solution is a lowest-common-denominator_solution, and that_common denominator gets lower and lower as_the_network of users, devices, and services_grows._Thus, if one attempts to create_a_unified_user interface with an application_server, one ends up with a_result where general-purpose (rather than task-specific and personalized) resources_or controls are_exposed. The user must manually_navigate_through_these resources or controls at runtime to manually extract desired_data and_must carry information_from step to step (i.e. the user must browse).
Hence, what_is needed is a method and an_apparatus that enables an application to interact with a user without_suffering from the