Message:

<p>[QUOTE=&quot;kirispupis, post: 8233596, member: 118780&quot;]I believe the algorithm is different. You can divide it into two parts - pre-bid and live.</p><p><br /></p><p><b>Pre-bid</b></p><p>Given a bid for x CHF on item foo:</p><p>Is the bid higher than the current?</p><p>&nbsp;&nbsp;&nbsp; No - ignore the bid</p><p>&nbsp;&nbsp;&nbsp; Yes - Has this user already placed a bid for the item?</p><p>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; No - Enter the bid as a new row in the table</p><p>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; Yes - update the existing bid for the new amount</p><p><br /></p><p>The logic that displays the current max is separate. </p><p>Choose the top two rows by price.</p><p>&nbsp;&nbsp; Is the lower value plus the bid increment greater than the higher value?</p><p>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; No - display the lower value plus the bid increment</p><p>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; Yes - display the higher value</p><p><br /></p><p><b>Live</b></p><p>Given a bid for x CHF on item foo:</p><p>Enter the bid into the system</p><p>Validation that the bid is at least one increment higher than the current is done on the client, though presumably it&#039;s done again here for data security.</p><p><br /></p><p>The logic that displays the current max:</p><p>Choose all the live rows and the top pre-bid row.</p><p>Similar logic to the above, but factoring in pre-bids and live bids.[/QUOTE]</p><p><br /></p>

Your name or email address:

Do you already have an account?

• No, create an account now.
• Yes, my password is:
• Forgot your password?

Stay logged in