[eoxserver-dev] RFC 10 "SOAP Proxy" - starting implementation.

[Stephan Meißl]

Milan,

adding the functionality to be able to POST the WCS requests to a
configurable URL is a valuable functionality anyway as it might be used
with any WCS server.

However, we might want find a more clever solution for the integration
of the SOAP Proxy and EOxServer to promote performance optimization. I'm
thinking of a solution where the requests and results are directly
passed in the memory. Stephan K. once mentioned a maybe possible
solution but I can't recall it right now.

Anyway, I think I'm trying to say I agree to proceed with the URL
solution but eventually we might find a better solution for our special
case.

cu
Stephan


On Mon, 2011-06-06 at 12:36 +0200, Novacek, Milan wrote: 
> Hi All,
>   I'm planning to put the soap_proxy into the eoxserver/soap_proxy svn this week, as the implementation of RFC 10.
> Initially I'll just transfer the existing code from the o3s project, but at some point we should discuss further integration with eoxserver.
> In particular, during the code sprint we raised the question of communication with the 'back-end'.
> For now, the 'back-end' is mapserver, and it is invoked by means of fork/exec, with data being passed through pipes.
> The question is should we invoke eoxserver instead - and instead of fork/exec should we just POST the output to a URL?  In practice the URL would in most cases be configured to be a localhost:eoxeserver instance.
> 
> Milan Novacek 
>