2011
DOI: 10.1016/j.future.2010.12.015
|View full text |Cite
|
Sign up to set email alerts
|

Web services workflow with result data forwarding as resources

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

1
5
0

Year Published

2011
2011
2014
2014

Publication Types

Select...
3
2

Relationship

0
5

Authors

Journals

citations
Cited by 7 publications
(6 citation statements)
references
References 2 publications
1
5
0
Order By: Relevance
“…The performance gains are higher when the workflow process larger data, similarly to the trend shown by Zhang et al in [24] where data was forwarded as WSRF resources. In contrast to Zhang et al's implementation, our data-flow delegation support is built on top of a standard web service framework.…”
Section: Discussionsupporting
confidence: 65%
See 1 more Smart Citation
“…The performance gains are higher when the workflow process larger data, similarly to the trend shown by Zhang et al in [24] where data was forwarded as WSRF resources. In contrast to Zhang et al's implementation, our data-flow delegation support is built on top of a standard web service framework.…”
Section: Discussionsupporting
confidence: 65%
“…The idea was realized using WSRF 8 resources. Zhang et al [24] came up with a similar approach suggesting to forward the intermediate data as WSRF resources directly from one web service to another in the process of orchestration. It is realized by extending an existing WSRF-compliant web services framework with data-forwarding capabilities.…”
Section: Related Workmentioning
confidence: 99%
“…In [8], a similar approach is proposed, which built complex applications from a high level workflow specification by applying contingency planning technique. However, the drawback of these techniques is high computation complexity, which often means that only suboptimal solution can be obtained by some heuristic functions.…”
Section: Related Workmentioning
confidence: 99%
“…The performance of the proposed algorithm (Evolution-strategy based Service Composition Algorithm, ESCA) are compared with three classic composition policy, which includes Global Composition Optimization Algorithm [8] (GCOA), Local Composition Optimization Algorithm [16] (LCOA), and Agent-based Service Composition Algorithm [20] (ASCA). Four QoS measurements are all considered separately in our experiments, and experimental results are shown in Figure 2 and Figure 3.…”
Section: Performance Comparisonmentioning
confidence: 99%
“…Habich et al have foreseen the need to decouple service implementation and data transfers in [22], but they cannot achieve full transparency, since plain clients are prevented from invoking those services that employ their framework. Finally, two interesting approaches are described in [24] and [25], where the data-transfers in workflows are addressed. The former takes advantage of service-proxies to share data, without involving the workflow engine; the latter introduces the state concept in workflows, to share intermediate data among successive services.…”
Section: Performance Evaluationmentioning
confidence: 99%