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

Detector of VFS high level events related to client side state #1832

Closed
dkuleshov opened this issue Jul 18, 2016 · 2 comments
Closed

Detector of VFS high level events related to client side state #1832

dkuleshov opened this issue Jul 18, 2016 · 2 comments
Assignees
Labels
kind/enhancement A feature request - must adhere to the feature request template.
Milestone

Comments

@dkuleshov
Copy link

Overview

The idea is to provide a detector or detectors to be able to transfer all client side related events that happens on VFS through some event transport from server to client.

Description

We need to be able to track events that impact client side and happens on server side on virtual file system so we could properly correspond. The most obvious example of such detector usage is tracking of file content changes. The workflow is the following:

  • A user opens a file in IDE editor (a new editor tab with file's content)
  • Client-side sevice tracks sees state changes and reports to the server-side that a file is opened
  • Now server-side detector is aware of that and starts tracking of that file's state on VFS
  • It watches and knows when changes (irrespective of source) are made
  • It informs (via event transport) client-side that file's content is changed
  • Client updates file's content in an editor's tab
@dkuleshov dkuleshov added kind/enhancement A feature request - must adhere to the feature request template. sprint/next team/ide labels Jul 18, 2016
@dkuleshov dkuleshov self-assigned this Jul 18, 2016
@vparfonov vparfonov added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. sprint/current and removed sprint/next labels Jul 20, 2016
@dkuleshov dkuleshov added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Aug 2, 2016
@dkuleshov dkuleshov removed the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Sep 18, 2016
@dkuleshov dkuleshov added this to the 5.0.0-M1 milestone Sep 18, 2016
@TylerJewell
Copy link

@dkuleshov - can you cross-link the PR for this please?

@dkuleshov
Copy link
Author

dkuleshov commented Sep 19, 2016

This issue was resolved under #2339

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template.
Projects
None yet
Development

No branches or pull requests

3 participants