Could we remove callnum from Koji Hub? It would make the protocol
simpler. Currently clients authenticate new sessions very frequently,
putting a lot of stress on the hub's database. It would be easier to
use the Koji API if we did not have to keep track of a callnum integer
On Sun, Dec 16, 2018 at 8:59 PM Ken Dreyer <ktdreyer(a)ktdreyer.com> wrote:
> Hi folks,
> I was reading in the source about callnum and wondering: what is the
> purpose of callnum?
> Is it a security feature, or just a way to maintain write operation order?
> It looks like Koji writes a new callnum integer to the database for
> every authenticated RPC, even if that RPC is only doing a read-only
> operation like getBuild.
> - Ken