On Sat, Jun 7, 2014 at 12:34 AM, Gabriel Roldan <[email protected]>
wrote:
> Chiming in where nobody calls me, but what if the response returned a URL
> where to get the raw data from instead of the Base64 encoded data? Too 90's
> I know (ArcIMS memories anyone?), but I'd seriously consider that given the
> options. A expiration time for the response, whether it'll be saved to disk
> and deleted after some time, or computed on the fly out of the URL hints,
> etc would be up to each process to decide?
>
Yes, WPS allows the binary data to be linked instead of being embedded in
the response document (or being
a direct raw return), however, it's not the server choice, it's the client
that requests things one way or the other,
and if nothing specific is requested, the standard mandates the inline
base64 response.
So, we need to be able to support both inline based 64 encoding, and linked
response, and raw direct responses.
We do the last two (the most reasonable ones imho) but we don't support the
first: this has to be amended,
since it makes the server not specification compliant
Cheers
Andrea
--
==
Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK
for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
