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
The BurnablePayment contract doesn't actually do any processing when the autorelease becomes available to the worker; the only thing that makes it "available" is that the require condition in triggerAutorelease "require(now >= autoreleaseTime)" will pass.
Because there is no processing, and no event triggered, the server currently has no way of knowing when this happens. This is unfortunate from a user experience perspective; a Buyer has an obvious interest in knowing that he can trigger the autorelease. A related feature would be to send out notifications when the autorelease is "coming soon"; this has utility for the Seller.
This isn't exactly trivial to set up though. The server would need to perform the above mentioned condition manually. Also, as things are currently written, there is an assumption that each notification originates from an event... Adding this feature violates that assumption, which means something will have to be rebuilt (for example, the "notifyParties" function takes an address and an event, but here there is no event).
The text was updated successfully, but these errors were encountered:
The BurnablePayment contract doesn't actually do any processing when the autorelease becomes available to the worker; the only thing that makes it "available" is that the require condition in triggerAutorelease "require(now >= autoreleaseTime)" will pass.
Because there is no processing, and no event triggered, the server currently has no way of knowing when this happens. This is unfortunate from a user experience perspective; a Buyer has an obvious interest in knowing that he can trigger the autorelease. A related feature would be to send out notifications when the autorelease is "coming soon"; this has utility for the Seller.
This isn't exactly trivial to set up though. The server would need to perform the above mentioned condition manually. Also, as things are currently written, there is an assumption that each notification originates from an event... Adding this feature violates that assumption, which means something will have to be rebuilt (for example, the "notifyParties" function takes an address and an event, but here there is no event).
The text was updated successfully, but these errors were encountered: