Feat: A2A Server (under development)
Description
Integrating the A2A server into Camel-AI. This includes two main components: the A2A Server and the A2A Client. The A2A Server is responsible for creating a server that enables communication between different models. The A2A Client connects to the A2A agent and sends tasks for processing. I would like to discuss possible approaches for integrating this system within the Camel-AI architecture. Fixing #2162
Checklist
Go over all the following points, and put an x in all the boxes that apply.
- [x] I have read the CONTRIBUTION guide (required)
- [x] I have linked this PR to an issue using the Development section on the right sidebar or by adding
Fixes #issue-numberin the PR description (required) - [x] I have checked if any dependencies need to be added or updated in
pyproject.tomlanduv lock - [x] I have updated the tests accordingly (required for a bug fix or a new feature)
- [ ] I have updated the documentation if needed:
- [x] I have added examples if this is a new feature
If you are unsure about any of these, don't hesitate to ask. We are here to help!
Hi @GitHoobar , sorry for any inconvenience. I’ve just started my open-source contribution journey, so I really appreciate your guidance. Please feel free to correct me—I'll do my best to avoid mistakes next time!
s
Hi @GitHoobar , sorry for any inconvenience. I’ve just started my open-source contribution journey, so I really appreciate your guidance. Please feel free to correct me—I'll do my best to avoid mistakes next time!
sure, no worries. I would say I will give it a proper review after you complete it. So for you is this PR ready/completed?
s
Hi @GitHoobar , sorry for any inconvenience. I’ve just started my open-source contribution journey, so I really appreciate your guidance. Please feel free to correct me—I'll do my best to avoid mistakes next time!
sure, no worries. I would say I will give it a proper review after you complete it. So for you is this PR ready/completed?
No i just want to ask that am i implementing this correctly architectural wise?
putting this on draft