Skip to content

Conversation

@DeepDiver1975
Copy link
Member

128 1 1

@DeepDiver1975 DeepDiver1975 added this to the 9.2 milestone Nov 17, 2016
@mention-bot
Copy link

@DeepDiver1975, thanks for your PR! By analyzing the history of the files in this pull request, we identified @icewind1991 to be a potential reviewer.

@DeepDiver1975 DeepDiver1975 force-pushed the publish-etag-change-to-event-dispatcher branch from 68d43e4 to 18a9353 Compare November 22, 2016 08:07
@DeepDiver1975 DeepDiver1975 force-pushed the publish-etag-change-to-event-dispatcher branch from 18a9353 to 94cb3f2 Compare November 22, 2016 08:43
@guruz
Copy link
Contributor

guruz commented Nov 22, 2016

  • Support for share(d) folders
  • Add etag transition in message: old etag AND new etag
  • If possible also add the fileId (can help the client at a later stage, i had some ideas)

FYI @PVince81

@DeepDiver1975
Copy link
Member Author

If possible also add the fileId (can help the client at a later stage, i had some ideas)

I wanted to keep the load minimalistic - the idea is to only send a notification for the root etag change.

@DeepDiver1975
Copy link
Member Author

Add etag transition in message: old etag AND new etag

with the current approach this will be problematic since the etag is computed and we don't have the explicit change available in the db

@DeepDiver1975
Copy link
Member Author

Support for share(d) folders

agreed

@DeepDiver1975 DeepDiver1975 deleted the publish-etag-change-to-event-dispatcher branch December 15, 2016 15:26
@lock
Copy link

lock bot commented Aug 4, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants