To interact with inline buttons and chosen result items, some necessary data is included with that item to distinguish it from others. This process is hard-coded and has many downsides like adding difficulty in updating codes after the encoding changes and so on. One solution is to put the data of the encoding in the ArangoDB and send the key of the document as the id field. Once interaction with a chosen inline result or inline button is made, by the returned id field one can retrieve the data needed to complete the action intended by the interaction. This way the mentioned problems will be solved. On the other hand, the amount of data made by this solution will grow exponentially if many queries are made by users. A requirement for the proposed method is the ability to support high-speed and low-latency data retrieval and writing operations. ArangoDB is a good candidate, however, if there are better alternatives, they can be used instead.
To interact with inline buttons and chosen result items, some necessary data is included with that item to distinguish it from others. This process is hard-coded and has many downsides like adding difficulty in updating codes after the encoding changes and so on. One solution is to put the data of the encoding in the ArangoDB and send the key of the document as the
idfield. Once interaction with a chosen inline result or inline button is made, by the returnedidfield one can retrieve the data needed to complete the action intended by the interaction. This way the mentioned problems will be solved. On the other hand, the amount of data made by this solution will grow exponentially if many queries are made by users. A requirement for the proposed method is the ability to support high-speed and low-latency data retrieval and writing operations. ArangoDB is a good candidate, however, if there are better alternatives, they can be used instead.