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

revised handling of handling object in process that publishes it #13

Merged
merged 16 commits into from
Sep 7, 2013

Conversation

yosefd
Copy link
Member

@yosefd yosefd commented Aug 15, 2013

If object publishes object, the file doesn't make any interest to itself. The state is maintained to what is in memory.

notifications come from initial subscription and from change on the
object. the race was possible. now completion of publishing comes when
object is loaded and it is equal to the published.
assume that there is only one publisher for the same object, which was
always the rule of the game.
following notification can swallow previous. this is legitimate.
this allows to publish concurrently from the same application and be
sure the completion of publishing would be satisfied.
Change in object got wiped upon publishing completion.
This is problematic from usage perspective and require changes change in
how rebus handles published data in the same process
published files are managed locally.
@yosefd
Copy link
Member Author

yosefd commented Aug 15, 2013

@saary @amitmach
Simplifying rebus to handle publishing from the same process better.

yosefd added a commit that referenced this pull request Sep 7, 2013
revised handling of handling object in process that publishes it
@yosefd yosefd merged commit fdf415d into master Sep 7, 2013
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

Successfully merging this pull request may close these issues.

1 participant