Caching for Sensor Web REST API

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Caching for Sensor Web REST API

Anton Egorov
Hello, my name is Anton and I'm trying to accomplish code challenges
about the caching for Timeseries REST API.
I'm a little bit confused by the third question:
"Have a look how request handling is done and come up with suggestions
how the requests can be optimized to reduce network traffic"
After reading the Timeseries API spec I have a notion that the major
part of traffic belongs to the timeseries responses (responses from
timeseries proxy to clients). Is it true? And if it's true, than why
is it important to optimize the requests? Won't it be more helpful to
reduce the amount of timeseries traffic?
_______________________________________________
GSoC mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/gsoc
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caching for Sensor Web REST API

Henning Bredel
Hey Anton,

thanks for your interest in this project idea.

You're correct, that responses have most potential being optimized. However,
optimizing traffic also comprises other things like what requests are needed to
satisfy a certain workflow (a response may not deliver all needed information
for a use case).

Do not lay too much focus on that detail.

Note: I'll have to exchange "Code Challenge 2" as there is a new dev line of the
SOS proxy which overhaules the old restful-timeseries-proxy. I will do this
afterwards, or tomorrow.

Nevertheless, you think of ideas about how caching can be implemented and where
it can make sense. Feel free to discuss your ideas over this list or directly
with Simon and me.

Best

  Henning

On 28.02.2017 22:30, Anton Egorov wrote:

> Hello, my name is Anton and I'm trying to accomplish code challenges
> about the caching for Timeseries REST API.
> I'm a little bit confused by the third question:
> "Have a look how request handling is done and come up with suggestions
> how the requests can be optimized to reduce network traffic"
> After reading the Timeseries API spec I have a notion that the major
> part of traffic belongs to the timeseries responses (responses from
> timeseries proxy to clients). Is it true? And if it's true, than why
> is it important to optimize the requests? Won't it be more helpful to
> reduce the amount of timeseries traffic?
>

--
Henning Bredel
52°North Initiative for Geospatial Open Source Software GmbH
Martin-Luther-King-Weg 24
48155 Münster, Germany
E-Mail: [hidden email]
http://52north.org/
Twitter: @FiveTwoN
General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk
Local Court Muenster HRB 10849
_______________________________________________
GSoC mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/gsoc
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Caching for Sensor Web REST API

Anton Egorov
Thank you for your reply. I'll try the new steps.


2017-03-02 12:06 GMT+03:00 Henning Bredel <[hidden email]>:
Hey Anton,

thanks for your interest in this project idea.

You're correct, that responses have most potential being optimized. However,
optimizing traffic also comprises other things like what requests are needed to
satisfy a certain workflow (a response may not deliver all needed information
for a use case).

Do not lay too much focus on that detail.

Note: I'll have to exchange "Code Challenge 2" as there is a new dev line of the
SOS proxy which overhaules the old restful-timeseries-proxy. I will do this
afterwards, or tomorrow.

Nevertheless, you think of ideas about how caching can be implemented and where
it can make sense. Feel free to discuss your ideas over this list or directly
with Simon and me.

Best

  Henning

On 28.02.2017 22:30, Anton Egorov wrote:
> Hello, my name is Anton and I'm trying to accomplish code challenges
> about the caching for Timeseries REST API.
> I'm a little bit confused by the third question:
> "Have a look how request handling is done and come up with suggestions
> how the requests can be optimized to reduce network traffic"
> After reading the Timeseries API spec I have a notion that the major
> part of traffic belongs to the timeseries responses (responses from
> timeseries proxy to clients). Is it true? And if it's true, than why
> is it important to optimize the requests? Won't it be more helpful to
> reduce the amount of timeseries traffic?
>

--
Henning Bredel
52°North Initiative for Geospatial Open Source Software GmbH
Martin-Luther-King-Weg 24
48155 Münster, Germany
E-Mail: [hidden email]
http://52north.org/
Twitter: @FiveTwoN
General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk
Local Court Muenster HRB 10849


_______________________________________________
GSoC mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/gsoc
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Loading...