Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely: The distributed embedded systems industry is poised to leverage emerging real-time operating systems, such as Inferno Windows CE, EPOC, and Palm OS to support mobile communication applications, such as electronic mail, Internet browsing, and network management. Ideally, these applications can be developed using standard middleware components like CORBA to improve their quality and reduce their cost and cycle time. Hover, stringent constraints on memory available in embedded systems imposes a severe limit on the footprint of CORBA middleware.  provides three contributions to the study and design of small footprint, embedded CORBA middleware. First,  describe the optimizations used to develop the protocol engine and CORBA IDL compiler provided by TAO, which is our real-time CORBA implementation. TAO's IDL compiler produces stubs that can use either compiled and/or interpretive marshalling. Second,  compare the performance and footprint of TAO IDL compiler-generated stubs and skeletons that use compiled and/or interpretive marshalling for a wide range of IDL data types. Third,  illustrate the benefits of the small footprint and efficiency of TAO IDL compiler-generated stubs and skeletons for CORBA object services implemented using TAO. The results comparing the performance of the compiled and interpretive stubs and skeletons indicate that the interpretive stubs and skeletons perform beten 75-100% of the compiled stubs and skeletons for a wide range of data types. Hover the code size for the interpreted stubs and skeletons was beten 26-45% and 50-80% of the compiled stubs and skeletons, respectively. These results indicate a positive step towards implementing high performance, small footprint middleware for distributed embedded systems.
['Aniruddha Gokhale', 'Douglas C. Schmidt']
I am writing a research paper on a idea Techniques for optimizing CORBA middleware for distributed embedded systems
[{"from": "human", "value": "I am writing a research paper on a idea Techniques for optimizing CORBA middleware for distributed embedded systems"}, {"from": "gpt", "value": "Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely: The distributed embedded systems industry is poised to leverage emerging real-time operating systems, such as Inferno Windows CE, EPOC, and Palm OS to support mobile communication applications, such as electronic mail, Internet browsing, and network management. Ideally, these applications can be developed using standard middleware components like CORBA to improve their quality and reduce their cost and cycle time. Hover, stringent constraints on memory available in embedded systems imposes a severe limit on the footprint of CORBA middleware.  provides three contributions to the study and design of small footprint, embedded CORBA middleware. First,  describe the optimizations used to develop the protocol engine and CORBA IDL compiler provided by TAO, which is our real-time CORBA implementation. TAO's IDL compiler produces stubs that can use either compiled and/or interpretive marshalling. Second,  compare the performance and footprint of TAO IDL compiler-generated stubs and skeletons that use compiled and/or interpretive marshalling for a wide range of IDL data types. Third,  illustrate the benefits of the small footprint and efficiency of TAO IDL compiler-generated stubs and skeletons for CORBA object services implemented using TAO. The results comparing the performance of the compiled and interpretive stubs and skeletons indicate that the interpretive stubs and skeletons perform beten 75-100% of the compiled stubs and skeletons for a wide range of data types. Hover the code size for the interpreted stubs and skeletons was beten 26-45% and 50-80% of the compiled stubs and skeletons, respectively. These results indicate a positive step towards implementing high performance, small footprint middleware for distributed embedded systems."}]