1 / 10

Future Directions in Middleware Research and Technology

Future Directions in Middleware Research and Technology. Fabio Kon kon@ime.usp.br Department of Computer Science University of São Paulo, Brazil http://www.ime.usp.br/~kon. Main Issues. Component-Based Software Automatic Configuration Adaptive Systems Separation of Concerns / Reflection

kathleen-patterson
Download Presentation

Future Directions in Middleware Research and Technology

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Future Directions in MiddlewareResearch and Technology Fabio Kon kon@ime.usp.br Department of Computer Science University of São Paulo, Brazil http://www.ime.usp.br/~kon

  2. Main Issues • Component-Based Software • Automatic Configuration • Adaptive Systems • Separation of Concerns / Reflection • Ubiquitous Computing • Social Aspects University of Tromsø

  3. Component-Based Software • Development: we need tools for • writing components • assembling components • debugging and testing • Deployment • standard environments • INTEROPERABILITY • Systems • Education But, it’s still our only alternative! University of Tromsø

  4. Automatic Configuration • Past: many users per computer • Present: few computers per user • Future: hundreds (thousands ?) computing devices per user • Solutions: 1. Static configuration from manufacturer 2. Automatic Configuration University of Tromsø

  5. Recent Advances in Automatic Configuration • 2K: some ideas, a nice prototype, many problems. • Debian Linux: limited scope, very robust and extremely useful implementation. • Major problem: how to specify what a component needs (prerequisites). • Prerequisite specification language • Prerequisite generator • (in fact, we need meta-information about components, systems, and environments) University of Tromsø

  6. Future Work in Automatic Configuration • Study prerequisite specification in Enterprise Java Beans, CORBA Component Model, .NET. • Investigate • how to generate them automatically; • how to use them for automatic configuration. University of Tromsø

  7. Adaptive Systems • One size does not fit all. • Environments are becoming more and more dynamic. • So, we need 1. generic model/framework for building adaptive systems; 2. compose repertoire of adaptations when designing new systems. University of Tromsø

  8. Separation of Concerns Functional Aspects vs. Non-Functional Aspects • Traditional approach (e.g., OO) is not enough • Reflection seems to be the most effective and flexible way of doing it. • Aspect-Oriented Programming (AOP) • a promising idea • but still very limited University of Tromsø

  9. Ubiquitous Computing • It will happen • most solutions are still ad hoc • Gaia OS University of Tromsø

  10. But • Why are we doing this? • For whom we are doing this? • Bill Gates and co.? • Multi-billion $ companies? • The 10% of the people who have Internet access? • What about the other 90%? • Open Software! • Free Software! University of Tromsø

More Related