What's the purpose of EventQueue?

[matino]

Hi,

I'm wondering what's the idea behind the communication with agent executor via the EventQueue? It seems like the communication would have been much simpler if it was via some kind of predefined response format. Can somebody explain this to me please?

[gesho]

that's how (message format left against complexities and choices of transmission protocol) it is in raw samples. and then you are left with need for lower level implementations, where you need to negotiate protocol between server and client. should your msg be delivered through sync / sse-streaming / push? if you look at task manager there it was left with a lot to handle.

here in sdk you are handed queue which abstracts earlier complexity. you put you message(s) in it and it will be delivered in spec compliant manner.

sdk and queue bring DX to a point that is commonly expected from a platform/sdk: you dont have to worry about protocol negotiation, you hand in your message to an communication service abstraction.

[matino]

you dont have to worry about protocol negotiation

I don't really understand what do you mean here. As a SDK consumer, I need to implement an agent executor class that implements certain interface. There's no protocol to negotiate here.

here in sdk you are handed queue which abstracts earlier complexity. you put you message(s) in it and it will be delivered in spec compliant manner.

Well, IMO it all comes down to the same thing - you either need to yield the correct response (TaskStatusUpdateEvent or TaskArtifactUpdateEvent), or manipulate the EventQueue to push the correct objects. The former being much more complex in the implementation (all additional class like EventConsumer, ResultAggregator, proper consuming etc) and prone to subtle queueing bugs (like #111).

I'm wondering what was the reasoning behind such implementation.