You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is currently sensing the changes on the tail of the file and missing any change above the last line that an Actor does.
I plan to extend to sense any change in any part of the file, as well as the nature of the change ( Create, Update, Delete).
This will give it CDC ( Change Data Capture ) properties, making the code more able to cope with different use cases.
The existing tailing will be unchanged so will not break the API or logic / behaviors you depend on from this code.
Another use case is do exactly the same style of sensing but on a whole File Hierarchy. So the server would be given a Folder path, and do Directory level change detection as well as File level change detection.
The text was updated successfully, but these errors were encountered:
gedw99
changed the title
Only sensing last line change Create action. Propose to extend to sense any line and nature of change.
Currently sensing last line change Create action. Propose to extend to sense any line change and the nature of that change.
May 26, 2023
The easiest way to add the CDC is to add a second phase.
The chronology of the code is like this:
File change detected, which already works now.
Run a diff of after against before using standard Unified Diff protocols. That will give the change and nature of the change
Log out to cli.
Then it is up to the developer what they want to do with that. Typically you Broadcast it and the other actor patches or does a transformation based on custom logic.
Note that the current tailing fails in that it gives the wrong answer to the cli when a change is made anywhere with the file. It works correctly with creates on the last line only.
It is currently sensing the changes on the tail of the file and missing any change above the last line that an Actor does.
I plan to extend to sense any change in any part of the file, as well as the nature of the change ( Create, Update, Delete).
This will give it CDC ( Change Data Capture ) properties, making the code more able to cope with different use cases.
The existing tailing will be unchanged so will not break the API or logic / behaviors you depend on from this code.
Another use case is do exactly the same style of sensing but on a whole File Hierarchy. So the server would be given a Folder path, and do Directory level change detection as well as File level change detection.
The text was updated successfully, but these errors were encountered: