Hello everyone,
Are there plans to add support for the Range header from the HTTP/1.1 specification? In other words, will we be able to specify a byte range for a WCS call and only retrieve the specified portion of the data?
Thanks,
David Rogers
Software Engineer
General Dynamics Information Technology
Hi David,
I’m not aware of any such plan.
Funny you ask though, we were discussing internally about DS-EO (download services for EO)
that in the GetProduct call require range support… but the service is mostly geared towards downloading
static files, where range access can be optimized.
Adding the same for WCS would require encoding the entire file anyways, to just return a part of the output… hum… if done
like that, I guess it could be implemented as a servlet filter of sorts, just throwing away the bytes that we don’t need to
return to the client. So, pretty generic functionality, I would not be against adding it as a general functionality that can be turned on by the admin.
One issue I see is that in general we do not know how large the output will be, so we cannot set the content-length,
however, be aware it could be “dangerous”, people might use it as a “download accelerator” would, and make the server encode
the same WCS image many times in parallel, thus increasing the load quite a bit (by blindly creating a set of ranges for
download, some of which might go beyond the end of file.
Cheers
Andrea
On Tue, Jun 14, 2016 at 6:09 PM, Rogers, David <David.Rogers@anonymised.com> wrote:
Hello everyone,
Are there plans to add support for the Range header from the HTTP/1.1 specification? In other words, will we be able to specify a byte range for a WCS call and only retrieve the specified portion of the data?
Thanks,
David Rogers
Software Engineer
General Dynamics Information Technology
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.