Quote from: Lytse on July 21, 2013, 12:50:53 PM

Quote from: Rannasha on July 21, 2013, 12:19:50 PM

Quote from: Lytse on July 21, 2013, 11:56:38 AM

Quote from: Rannasha on July 21, 2013, 11:36:56 AM

As for the bot-advantage, I believe the order is processed when you reach the message-page, so there is no delay in actually having the order listed, just a short delay in seeing the new orderbook.

So... There is an andvantage, good to know.

Thanks for the information.

I'm not even sure if it's an advantage. The event-flow when submitting orders is as follows:

Manual / person:
Submit order ----> Result page --(wait or click)--> Reloaded asset-page

Bot:
Submit order ----> Result response

In both cases, the actual order is listed at the first arrow, directly after the submission has been sent. All a bot gets is a response that tells it whether the order was successfully submitted. A normal person gets the same response on the intermediate page that redirects back to the asset-page after a few seconds (or when the user clicks a link).

In my browser it is not possible to click.... Huh

After submitting, there's a box that says "Redirect to /security/DMS.SELLING in 7 seconds..." (obviously different for different assets and the timer counts down). The "/security/DMS.SELLING" part of this is a direct link to the asset-page.

Quote

There is an advantage when you get the information sooner, the diagram is as follows:

Manual / person:
Submit order ----> Result page ------> (wait_time) -----> Reloaded asset-page

Bot:
Submit order ----> Result response
Submit request order book ---> order book

This advantage doesn't come from the design of BTCT though. You could have the order book open in a different browser tab and after clicking the submit order, go to that tab and refresh it.

Bots will always be able to beat humans with parallelized requests and faster information processing. That's a generic feature and independent of BTCT.