Skip to content

Design concept consultation #3

@TheEterna

Description

@TheEterna

hello,I have some opinions and doubts about the design of this project. I hope you can take some time to take a look,The suggested points are as follows:
I don't think it's necessary to divide classes such as Resourcecallback and Prompcallback into synchronous and asynchronous versions. Because there is no difference in its logic, only some universality difference in the return value. So this problem can be solved through dynamic transformation methods,the reference is the Toolcallback logic of spring ai mcp.

Perhaps, do you have any considerations for your design? I hope you can elaborate on the design concept of this project. I am particularly interested in knowing, and thank you very much for your reply.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions