Skip to content

Why is this SDK not generic, not SPI driven and designed around Spring Reactor ? #8

@cmoulliard

Description

@cmoulliard

Discussion

Why is this SDK not generic not designed using a SPI and implements Spring Reactor ?

As mentioned too part of a Java MCP SDK discussion here using what the JDK offers could be a better long term option for this project to get more contributors and allow non Spring projects like: quarkus, langchain4j, micronaut, etc to consume if we are not tight to a vendor technology.

If you are interested we could join our efforts to integrate what I did here within this project: https://github.com/snowdrop/acp-java-client. Of course, the general architecture should be review to design the SPI layer, api that we will use: CompletionStage, VirtualThread, etc, if we plan to use a declarative API where we would use Java Annotation etc

WDYT ?

@markpollack @benbrandt @maxandersen

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions