2013
DOI: 10.4018/978-1-4666-2089-6
|View full text |Cite
|
Sign up to set email alerts
|

Adaptive Web Services for Modular and Reusable Software Development

Abstract: The provision of individual, but also composed services is central in cloud service provisioning. We describe a framework for the coordination of cloud services, based on a tuple-space architecture which uses an ontology to describe the services. Current techniques for service collaboration offer limited scope for flexibility. They are based on statically describing and compositing services. With the open nature of the web and cloud services, the need for a more flexible, dynamic approach to service coordinati… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
8
0

Year Published

2014
2014
2018
2018

Publication Types

Select...
3
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(8 citation statements)
references
References 8 publications
0
8
0
Order By: Relevance
“…We are currently working on applying the theory of updatable choreographies/orchestrations in the context of session types for typing a concrete language with session spawning, where choreographies play the role of global types attached to sessions and we use orchestrations for checking, via typing rules, that the code actually conforms with the specified global types. In this context, extending our contract refinement theory [5,7,9,10,12] to updatable choreographies/orchestrations would make it possible to define a notion of semantic subtyping.…”
Section: Resultsmentioning
confidence: 99%
See 1 more Smart Citation
“…We are currently working on applying the theory of updatable choreographies/orchestrations in the context of session types for typing a concrete language with session spawning, where choreographies play the role of global types attached to sessions and we use orchestrations for checking, via typing rules, that the code actually conforms with the specified global types. In this context, extending our contract refinement theory [5,7,9,10,12] to updatable choreographies/orchestrations would make it possible to define a notion of semantic subtyping.…”
Section: Resultsmentioning
confidence: 99%
“…We, thus, define contract refinement as the coarsest preorder over behavioural contracts which preserves correct composition when applied to members of a set of behavioural contracts (one for each role of a choreography). See [5,6,7,8,9,10,11,12] for formal definitions considering several form of communications/notions of correct composition.…”
Section: Behavioural Contracts and Contract Refinementmentioning
confidence: 99%
“…We will therefore take terms C belonging to a generic set P con being any set of terms (generated by the syntax of a process algebra) that give rise to all possible behavioral contracts as their semantics (in the form of finite connected LTSes as in Definition 3.2). For instance P con can be basic CCS (with recursion) over L prefixes and extended with successful termination 1, see [13,2].…”
Section: Definition 32 (Behavioural Contract)mentioning
confidence: 99%
“…To this aim a foundational study about coarsest refinement preorders between behavioural contracts made it possible to decide whether a service discovered on the internet can be used to play the role of a service with a given desired contract in the context of a multi-party coordination (independently of the service discovered for the other roles) [2,12,11,10,7,6], or to play a certain role in a given choreography [13,9,8], without incurring in deadlocks (and furthermore guaranteeing termination under fairness assumption). More precisely, theories of behavioural contracts have been introduced which enable reasoning about correct service composition (contract compliance) and service substitutability (contract refinement preorder) under different assumptions concerning service communication: synchronous address [13,2,8] or name based [11,10,6] communication (invocations are directed to a certain role or just based on channel names as in CCS) with patient non-preemptable or impatient invocations (waiting admitted when invoking services, as in CCS communication, or not admitted, as for the ready-send primitive of the Message Passing Interface) [12,7], or asynchronous communication with queues [13,9].…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation