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

middleware: caching #30

Closed
miekg opened this issue Mar 20, 2016 · 2 comments
Closed

middleware: caching #30

miekg opened this issue Mar 20, 2016 · 2 comments

Comments

@miekg
Copy link
Member

miekg commented Mar 20, 2016

a caching middleware

@miekg
Copy link
Member Author

miekg commented Apr 13, 2016

Should we cache RRset or complete messages? The former is how you should do it, but what it that leads to a partial answer? Then you need to get fetch it from somewhere.. do you then invoke the next middleware? That could work.
Or you could cache complete answers, but then there is a problem of multiple clients with different buffer sizes (or even transport), i.e. you can't re-use a TCP message when a client comes asking via UDP.

The first approach makes most sense, it's RFC compliant, and if you find that answer incomplete just hand off to the next middleware.

@miekg
Copy link
Member Author

miekg commented Apr 16, 2016

question still is... when is an answer incomplete.... In this example it can be detected. www.miek.nl is a cname to a.miek.nl:

;; ANSWER SECTION:
www.miek.nl.        1800    IN  CNAME   a.miek.nl.
a.miek.nl.      1765    IN  A   139.162.196.78

So if I have the CNAME, but not the target, which is inbaliwick I should just hand hand off...?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant