Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server method enhanced caching support #1948

Closed
hueniverse opened this issue Sep 15, 2014 · 7 comments
Closed

Server method enhanced caching support #1948

hueniverse opened this issue Sep 15, 2014 · 7 comments
Labels
feature New functionality or improvement

Comments

@hueniverse
Copy link
Contributor

Server methods can be used as prerequisites and handlers. However, caching these methods is not possible if they return a stream or other non JSONifiable response.

The steps are to:

  • enhance catbox to support caching of streams
  • allow caching of delayed execution (e.g. method returns a stream, which is cached later after the stream is finished piping)
  • link cache policy with the HTTP response (cache-control and warning headers)

This issue replaces #1237, #1243, #1250, #1263

@hueniverse hueniverse added the feature New functionality or improvement label Sep 15, 2014
@fhemberger
Copy link

Is there any progress on this topic (or a rough plan when this issue will be addressed)? I'd love to use catbox-s3 directly via hapi configuration.

@hueniverse
Copy link
Contributor Author

Nope. I doubt it will make it into v8.0.

@devinivy
Copy link
Member

Any chance this will be added to the 9.0.0 milestone? Or might this make its way in before 9.0.0 since it may not require any breaking changes?

@hueniverse
Copy link
Contributor Author

I am not actively working on this but I'm also not inclined to put a help wanted label on it because I am unlikely to like other people's implementation for this :-). But if someone wants to give it a go...

@mugli
Copy link

mugli commented Apr 18, 2016

Any update on this?

@autarc
Copy link

autarc commented Apr 28, 2016

Second that, would also be interested for caching streams which are currently just piped through the reply interface. Its a while since the issue got created so it would be good to know from @hueniverse if there is is some progress or additional thoughts about an implementation.

@hueniverse
Copy link
Contributor Author

It's a feature I want to add but have no time or need for at this point. If someone wants to give it a try, I'm open to it, but historically, I've been pretty hostile to other people's code when touching these areas of the framework. If you really want to do it, start with catbox.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature New functionality or improvement
Projects
None yet
Development

No branches or pull requests

5 participants