potiuk commented on PR #23: URL: https://github.com/apache/comdev/pull/23#issuecomment-4887538121
> Another issue to consider: what about other tools that could benefit from long-term tokens? I guess it's up to those tools - since we are purely basing it on openapi - and openapi is implemented in server (and is part of the impleme manntation) - it's "good enough" to be implemented by others. > Does it make sense to replicate the code in every tool that could benefit from it? I guess it depends on the programming language - we have a common "Open API" layer describing API and it can be implemented by others. But if - as a maintainer of PonyMail, you think tha some libraries in a number ofntia programming languages is a good Idea - I am happy to produce a separate library in many languages. The "openapi" spec can be turned into a ready to use library, with documented interface and API - by just a matter of using one of the openapi generators. In airflow for example we generate a Python client library automatically from our openapi spec. And if PonyMail maintainers want to build and release such libraries - I am happy to automate generation of those - but I think it's more of PonyMail maintainers what they want to support - whether the API (this is what is supported today) or whether they want to also release and support libraries (in Airlfow we decided to only support Python library and we suggest our users to use generators to support the same interface in other libraries - and I think it's the **right** approach for maintainers to only support libraries in language they are comfortable with. But I think this is more of a discussion in https://github.com/apache/incubator-ponymail-foal/pull/321 than here. This one is just one of the implementations that I used to test the new API with - but if maintainers of Ponymail would like to support library in Python, I can help to build such library and use it in PonyMailMCP as well. No problem whatsoever. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
