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.

Sign up for GitHub

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

Jump to bottom

negative lookups are not cached #1

Closed
jfhg opened this issue Mar 8, 2013 · 0 comments
Closed

negative lookups are not cached #1

jfhg opened this issue Mar 8, 2013 · 0 comments
Assignees
@wizzard
Labels
enhancement

Comments

@jfhg
Copy link

jfhg commented Mar 8, 2013

When accessing a riofs mounted directory via proftpd, the ftp deamon checks for
a .ftpaccess file a lot.
If this file is not there, riofs asks s3 for that file on every access.
It would be cool if the fact that .ftpaccess is not existing could also be cached just as other metadata.
@ghost ghost assigned wizzard Mar 8, 2013
@sunxm sunxm mentioned this issue Oct 27, 2014
Closed
ThePythonicCow added a commit to ThePythonicCow/riofs that referenced this issue Jan 13, 2017
@ThePythonicCow
Etag fix skoobe#1: Upgrade riofs version from 0.7 to 0.8
9628f00 
Since the patches that follow this patch make a fairly substantial
change to how riofs recognizes that a cached file has changed on
the Amazon AWS S3 server (thus requiring invalidating the local cache),
I have therefore bumped the riofs version number.
ThePythonicCow added a commit to ThePythonicCow/riofs that referenced this issue Jan 14, 2017
@ThePythonicCow
Etag fix skoobe#1: Upgrade riofs version from 0.7 to 0.8
943daf8 
Since the patches that follow this patch make a fairly substantial
change to how riofs recognizes that a cached file has changed on
the Amazon AWS S3 server (thus requiring invalidating the local cache),
I have therefore bumped the riofs version number.
ThePythonicCow added a commit to ThePythonicCow/riofs that referenced this issue Jan 15, 2017
@ThePythonicCow
Etag fix skoobe#1: Upgrade riofs version from 0.7 to 0.8
ca26e0b 
Since the patches that follow this patch make a fairly substantial
change to how riofs recognizes that a cached file has changed on
the Amazon AWS S3 server (thus requiring invalidating the local cache),
I have therefore bumped the riofs version number.
ThePythonicCow added a commit to ThePythonicCow/riofs that referenced this issue Jan 15, 2017
@ThePythonicCow
Etag fix skoobe#1: Upgrade riofs version from 0.7 to 0.8
332a3c0 
Since the patches that follow this patch make a fairly substantial
change to how riofs recognizes that a cached file has changed on
the Amazon AWS S3 server (thus requiring invalidating the local cache),
I have therefore bumped the riofs version number.
ThePythonicCow added a commit to ThePythonicCow/riofs that referenced this issue Jan 15, 2017
@ThePythonicCow
Etag fix skoobe#1: Upgrade riofs version from 0.7 to 0.8
9355df4 
Since the patches that follow this patch make a fairly substantial
change to how riofs recognizes that a cached file has changed on
the Amazon AWS S3 server (thus requiring invalidating the local cache),
I have therefore bumped the riofs version number.
ThePythonicCow added a commit to ThePythonicCow/riofs that referenced this issue Jan 15, 2017
@ThePythonicCow
Etag fix skoobe#1: Upgrade riofs version from 0.7 to 0.8
1b9feec 
Since the patches that follow this patch make a fairly substantial
change to how riofs recognizes that a cached file has changed on
the Amazon AWS S3 server (thus requiring invalidating the local cache),
I have therefore bumped the riofs version number.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wizzard wizzard

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wizzard @jfhg