[Biogeosdi] Report from OGC meeting

Javier de la Torre jatorre at gmail.com
Thu Jul 19 00:20:02 CEST 2007

Hi Renato,

> impractical to send them as simple URL parameters. Anyway, if you
> discover a better way to do that in REST, please let me know!!

I think I might have a better approach, but I have to finish reading  
a bit to tell you more... again if you have the opportunity get  

> This means that by using REST, you would still need to deal with "low-
> level HTTP requests" (using PEAR or the new HTTP extension for PHP or
> any other library). By the way, for me REST also means "make full use
> of HTTP because it has many other useful features that most people
> don't even know". So I think that the most basic toolkit for a REST
> developer is to have a good HTTP library.

Right, but for the basics, you dont really need anything but just  
open a url... so, make things complicate where they need to be right?

> So in this case (createModel request), the only difference between
> using REST and SOAP considering those seven lines of low-level HTTP
> code, would be an additional line before sending the request:
> $xmlBody = WrapWithSoapEnvelope($xmlBody);

I still think that if you dont set the SOAPAction in the http header  
your gSOAP library will raise an error. And the problem with this is  
that once you have to start defining your own http headers to do a  
request then you cant use most of libraries to http request because  
they dont expose normally this functionality.

> Please don't consider the Perl client that I mentioned in my previous
> message a requirement to get things working. If you have a local copy
> of the openModeller source code, you can look at src/soap to find one
> file for each request and response of each operation (e.g.
> openModeller.getLayers.req.xml). I forgot that they were
> automatically generated by gSOAP and can be used as a reference.

Well, you used a Perl program, I used Oxygen SOAP debugger, and  
someone might get the sample code after checking out the server  
code... probably some documentation somewhere about this thing would  
help a lot, but then you start looking very much as REST,  
documentating the service in natural language :D


More information about the tdwg-content mailing list