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

Client side API #180

Open
tshemsedinov opened this issue Aug 30, 2018 · 0 comments
Open

Client side API #180

tshemsedinov opened this issue Aug 30, 2018 · 0 comments
Assignees

Comments

@tshemsedinov
Copy link
Member

We need to prepare globalstorage for running in browser and provide API for front-end application. So first implementation will be simple, just selecting from categories but it will return MemoryCursors.

Creating new cursor client-side globalstorage instance will pass query to server-side globalstorage instance and then it will create MemoryCursor from whole (not filtered) dataset holding in memory or from StorageProvider reading data from persistent storage. After that we will have client-side MemoryCursor connected with server-side MemoryCursor. Client-side MemoryCursor:

  • should hold dataset in memory (if it will be large 100 records we can send to the client first 100 records and total count, then send data bunches on request)
  • should hold metadata/schema of the dataset (not all fields, we need to filter schemas)
  • should pass operations to server-side MemoryCursors
  • server-side MemoryCursors should pass operations to not filtered MemoryCursor for memory caching and to StorageProvider for persistent storage
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants