You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If users want to customize the HTTP interactions for models that support stream, they frequently have to provide a customized RestClient and WebClient which are customized using their own respective api. The user must have the skill to configure both the RestClient and the WebClient.
What if spring-ai offered the ability to configure a WebClient based on a RestClient configuration, this way the user only has to configure RestClient and spring-ai reads the configuration of the RestClient and configures the WebClient to match the settings in RestClient where the settings are common. This approach might reduce the effort required for users to perform simple common customizations.
This really feels like a boot issue, to provide configuration properties for all the http client libraries so that they can be configured. I do think the status quo ATM, for example to set timeouts or to enable logging of http requests is rather poor in terms of convenience from the foundational spring projects. Not sure why this hasn't been addressed already, can investigate.
If users want to customize the HTTP interactions for models that support stream, they frequently have to provide a customized RestClient and WebClient which are customized using their own respective api. The user must have the skill to configure both the RestClient and the WebClient.
What if spring-ai offered the ability to configure a WebClient based on a RestClient configuration, this way the user only has to configure RestClient and spring-ai reads the configuration of the RestClient and configures the WebClient to match the settings in RestClient where the settings are common. This approach might reduce the effort required for users to perform simple common customizations.
Related issues:
The text was updated successfully, but these errors were encountered: