Denis Caromel 1 Denis Caromel Joint work with Ludovic Henrio – Eric Madelaine et. OASIS members OASIS Team INRIA -- CNRS - I3S – Univ. of Nice Sophia-Antipolis, IUF Keynote talk at Formal Aspects of Component Systems, FACS, Prague, Sept. 2006 Theory to Practice in Distributed Component Systems
21
Embed
Denis Caromel Joint work with Ludovic Henrio – Eric Madelaine et. OASIS members OASIS Team
Theory to Practice in Distributed Component Systems. Denis Caromel Joint work with Ludovic Henrio – Eric Madelaine et. OASIS members OASIS Team INRIA -- CNRS - I3S – Univ. of Nice Sophia-Antipolis, IUF Keynote talk at Formal Aspects of Component Systems, FACS, Prague, Sept. 2006. - PowerPoint PPT Presentation
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Denis Caromel 1
Denis CaromelJoint work with Ludovic Henrio – Eric Madelaine et.
OASIS members
OASIS TeamINRIA -- CNRS - I3S –
Univ. of Nice Sophia-Antipolis, IUF
Keynote talk at Formal Aspects of Component Systems, FACS, Prague, Sept. 2006
Theory to Practice in Distributed Component Systems
Denis Caromel 2
Denis CaromelJoint work with Ludovic Henrio – Eric Madelaine et.
OASIS members
Theory to Practice in Distributed Component Systems
1. Distributed Objects: Active Objects2. Calculus: ASP3. Dist. Component Specification: GCM4. Middleware: ProActive5. Model Checking: Vercors
Statement a: Prog. Language – Model / Semantics Statement b.: Active Objects
Denis Caromel 3
Denis CaromelJoint work with Ludovic Henrio – Eric Madelaine et.
OASIS members
Practice to Theory to Practice in Distributed Component Systems
1. Distributed Objects: Active Objects2. Calculus: ASP3. Dist. Component Specification: GCM4. Middleware: ProActive5. Model Checking: Vercors
Statement a: Prog. Language – Model / Semantics Statement b.: Active Objects
Denis Caromel 4
Features for Scalable, Distributed
Objects and Components
• Asynchronous Calls
• 1st Class Futures
• Typed Groups
Denis Caromel 5
Features for Component Verifications
• Wait-by-Necessity
• Future Update can occur anytime (no consequences)
• No sharing
• No user-, code-level, concurrency and parallelism
• Insensitive Semantics to Distribution / Location