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

Blobs? #342

Open
shift-reality opened this issue Dec 8, 2019 · 1 comment
Open

Blobs? #342

shift-reality opened this issue Dec 8, 2019 · 1 comment

Comments

@shift-reality
Copy link

Hi. For what purpose client make this blob requests?
i understand what is not generate any traffic, just interest... Why?
3 requests with fixed interval (about 10 seconds)

blob1
blob2

@manusa
Copy link
Owner

manusa commented Dec 8, 2019

This is the way the asynchronous background-thread system for persistence works.

Each time the state is persisted a new WebWorker thread is started that performs data encryption and persists it in the IndexedDB storage of your browser.

This is part of the "magic" of Isotope and what makes it unique amongst any other Webmail solution. Data lives encrypted in your browser (and in your IMAP server, of course), but nothing lives in the server component of Isotope.

Isotope's implementation is using worker-loader which has the behavior you describe, so for each worker instance, a new Blob is created (no network traffic is generated).

The reason you see 3 requests is totally arbitrary and depends on the number of messages you've got in the active folder. If the folder has more messages you'll see more "blob" requests, as each batch of messages received from the messages SSE request will be persisted using the described technique.
image

You'll also be able to see these threads running in the Memory tab of Developer Tools:
image

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