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

Limitation of the global cache mechanism? #74

Closed
Arunm619 opened this issue Oct 18, 2021 · 3 comments
Closed

Limitation of the global cache mechanism? #74

Arunm619 opened this issue Oct 18, 2021 · 3 comments

Comments

@Arunm619
Copy link

Arunm619 commented Oct 18, 2021

Stackzy uses a gloabl caching mechanism, which works as a centralized caching system. Means, if someone decompiled WhatsApp, the next time you try to find the stack, it won't be decompiled and the result will be served from the cache.

  • What if the decompilation done was done long back, and the new requests with more recent APKs are also served with stale data.
@theapache64
Copy link
Owner

theapache64 commented Oct 19, 2021

We also store and match the versionCode of the APK decompiled. 😉

@theapache64
Copy link
Owner

@Arunm619 Good to close?

@theapache64
Copy link
Owner

Closing due to no response. Feel free to reopen

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

2 participants