IEEE International Conference on Web Services (ICWS 2007) 2007
DOI: 10.1109/icws.2007.139
|View full text |Cite
|
Sign up to set email alerts
|

Performance Evaluation and Modeling of Web Services Security

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
19
0
5

Year Published

2008
2008
2014
2014

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 32 publications
(24 citation statements)
references
References 2 publications
0
19
0
5
Order By: Relevance
“…In the year 2007, Shipping Chen, John Zic, Kezhe Tang, David Levy [4] presented a testing result for monitoring the performance overheads of WS due to WSS. The work includes a client that sends a request to WS for a list of data objects as customer records.…”
Section: Related Workmentioning
confidence: 99%
“…In the year 2007, Shipping Chen, John Zic, Kezhe Tang, David Levy [4] presented a testing result for monitoring the performance overheads of WS due to WSS. The work includes a client that sends a request to WS for a list of data objects as customer records.…”
Section: Related Workmentioning
confidence: 99%
“…The most attractive feature of WS is its interoperability in a heterogeneous environment, and exposing existing applications as a WS increases their reach to different client types. Security measures are not something that can be added in a certain system's architecture, without having thought of them and designed them at the very early stages (Chen et al, 2007). The integration of context into WS composition/transaction ensures that the requirements of and constraints on these WS (either security-or interoperability-oriented) are taken into account.…”
Section: Web Service Security Considerationsmentioning
confidence: 99%
“…The work that is most closely related to the work presented in this paper is by Chen, Zic, Tang, and Levy [3]; this work compares different security mechanisms in detail and addresses payload size. The contribution of the work described in this paper is the comparison of a larger range of payload types and sizes, analyses of different payload complexities, the secure conversation security mechanism, and mechanism startup costs, as well as the examination of the cost of security from the perspective of message size and resource usage.…”
Section: Related Workmentioning
confidence: 99%
“…One reason for the increase might be payload size. 3 The base payload of the Echo web service is 12 bytes, while that of Employee Details is approximately 112 bytes [26,27]. Considering that the call to the Employee Details service has no arguments while the Echo service has the same input as output, the roundtrip payload size with the Employee Details service is approximately 450% larger than that with the Echo (112 versus 24 bytes).…”
mentioning
confidence: 99%