Understand Publish Mechansim

Home Forums PeerfactSim Forum Understand Publish Mechansim

  • This topic has 1 reply, 1 voice, and was last updated 9 years ago by Matthias Feldotto.
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #860
    Chintan Parekh


    I have implemented a new functionality wherein on PublishDocument success I basically publish the attributes related to that document.
    There is no problem in publishing the attributes too but I just want to make sure that publsihing the 2nd document happens only after my document and all its attributes are published.

    I have delayed the operationSuccess for document till the last attribute. Only when the last attribute is published we get a document stored message. I was expecting this would solve the problem but still other documents start getting published in middle of attributes getting published.

    Is there any timer? because I have delayed the operationCallback till the last attributed publishSuccess..!

    Hoping to hear from you.

    Matthias Feldotto


    the FileSharing application in the moment is implemented in an independent way. This means that every publishing of documents is independent from each other and therefore it can also happen that two publish processes overlap. To prevent this, you have to publish all documents manually, for example through the actions file, or you have to implement a new publish process which handles this issues.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.

Comments are closed.