RE: GALEON report

• To: "Martin Daly" <Martin.Daly@xxxxxxxxxxx>
• Subject: RE: GALEON report
• From: i.delchev@xxxxxxxxxxxx
• Date: Wed, 8 Feb 2006 16:57:51 +0100 (CET)

Dear All,

We have added support for HTTP GET and POST requests in our WCS
implementation. Actually we have two different implementations - a servlet
which handles HTTP requests located at
http://mango.eecs.iu-bremen.de:8180/wcs/servlet/WcsServlet and an AXIS web
service which handles SOAP requests located at
http://mango.eecs.iu-bremen.de:8180/axis/services/WCS.

Please do test those services but before that please refer to
http://mango.eecs.iu-bremen.de:8000/~galeon/ for details.

For any technical difficulties or problems contact me at
i.delchev@xxxxxxxxxxxxx

Best regards,
Ivan Delchev


> http://mango.eecs.iu-bremen.de:8180/axis/services/WCS?REQUEST=GetCapabil
> ities&SERVICE=WCS&VERSION=1.0.0
>
> OK, I've read on a bit, and see that the service only supports SOAP
> requests, correct?  If so then our client cannot connect to your
> service, I'm afraid.
>
> We have always worked on the understanding that services had to support
> HTTP GET for the GetCapabilities, and then we would either automatically
> choose, or allow the user to choose, whether to use HTTP POST or HTTP
> GET from that point on.  If I recall correctly, it turned out that this
> (HTTP GET for GetCapabilities) was never mandated in any of the W*S
> specs, but that others had made the same assumption as us.
>
> So, if you were able to implement an HTTP GET GetCapabilities, e.g. as a
> wrapper for your SOAP implementation, then that would greatly aid
> interoperability for Cadcorp, and I suspect, for others.  This
> pebble-in-the-pond also ripples out to supporting HTTP GET and/or HTTP
> POST wrappers for the other requests, the SOAP interfaces not yet having
> been adopted by OGC, or implemented by us.
>
> Regards,
> Martin
>
>

• References:
  • RE: GALEON report
    • From: Martin Daly