Best practice of serviceId for AIServiceSelector

[HuskyDanny]

Since each chat completion instance needs a serviceId, and AIServiceSelector basically uses serviceId to select. Can I use $"service_{model_name}" as the name for the supported models?

My intention is to support multiple models like o3, 4o, claude. Since each of them needs an instance and a serviceId, so the serviceId to model is 11 mapping.

I post the question here because I am seeing the use of serviceId is more like a role based like chat_service, summarize_service. Is the model level granularity on serviceId a good practice? If not, how to get over the multiple models support scenario？

[moonbox3]

The service id -> service mapping is really any way you want it to behave. If you want $"service_{model_name}" to map to a specific service, that's completely fine. It's simply a way for you to define multiple key (service_id) to value (AI Service) so you can indeed switch back and forth between models easily, based on whatever internal logic you have.

[HuskyDanny]

Very clear, thanks