Comments on: Simple Recipe for SOAP Echo Service

By: Ivan Stojic

Ivan Stojic — Tue, 03 Oct 2006 07:10:20 +0000

I like the concept. It is a bit misleading to call it an echo server when in fact it doesn’t echo anything, but that’s a really small issue if all you are trying to do is to get a basic SOAP functionality working from your client.

Nice!

By: Parand Darugar

Parand Darugar — Wed, 23 Nov 2005 18:54:57 +0000

Stefan, excellent point, of course an echo server should echo the input, which this setup doesn’t. I used the term simply because the people who were originally looking to implement the “echo server” were returning simple static content.

What I’ve described here is a ping service or something like that. What we ended up doing was using a php script to embed a few pieces of info (eg. current time in miliseconds, ip address of calling party, etc) into the response so it’s not entirely static, but doesn’t echo the input either. The php document is basically an XML doc that has contents of the fields filled in by small php segments. I’ll post it one of these days.

By: Stefan Tilkov

Stefan Tilkov — Tue, 22 Nov 2005 23:14:00 +0000

I must be missing something, but isn’t an echo server supposed to return something *different* depending on the SOAP request? How can this be a static page?

By: Chris Radcliff

Chris Radcliff — Fri, 04 Nov 2005 18:33:20 +0000

Fantastic idea. It really undersores how _simple_ SOAP was supposed to be, and how complicated everyone makes it.

I’m pretty sure that the Apache prohibition against POSTing to a static page is a config option. Don’t quote me on that, but it’s worth looking into if you want to do real load testing without swamping the poor PHP/scripting system.