SOAP vs REST: Comparing a master-slave GA implementation

Details SOAP vs REST: Comparing a master-slave GA implementation SOAP vs REST: Comparing a master-slave GA implementation

2011-05-25

arxiv.org/abs/1105.4978v1

Computer Science

Neural and Evolutionary Computing

Paper 2 for the First International Workshop of Distributed Evolutionary computation in Informal Environments

Scientific paper

In this paper, a high-level comparison of both SOAP (Simple Object Access Protocol) and REST (Representational State Transfer) is made. These are the two main approaches for interfacing to the web with web services. Both approaches are different and present some advantages and disadvantages for interfacing to web services: SOAP is conceptually more difficult (has a steeper learning curve) and more "heavy-weight" than REST, although it lacks of standards support for security. In order to test their eficiency (in time), two experiments have been performed using both technologies: a client-server model implementation and a master-slave based genetic algorithm (GA). The results obtained show clear differences in time between SOAP and REST implementations. Although both techniques are suitable for developing parallel systems, SOAP is heavier than REST, mainly due to the verbosity of SOAP communications (XML increases the time taken to parse the messages).

Affiliated with

Also associated with

No associations

Rating

SOAP vs REST: Comparing a master-slave GA implementation does not yet have a rating. At this time, there are no reviews or comments for this scientific paper.

If you have personal experience with SOAP vs REST: Comparing a master-slave GA implementation, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and SOAP vs REST: Comparing a master-slave GA implementation will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFWR-SCP-O-191188