Leverage Odoo's session ID returned as a cookie value.

I'm not sure about XML RPC calls, but I see that when JSON RPC calls are made, Odoo does respond with a session ID for the call that was made, however odoo-rpc-client does not appear to be storing and re-using that session ID for authentication purposes.

The big drawback to this is that if we use odoo-rpc-client for ETL scripts which make thousands of calls to Odoo .. it means that Odoo will generate thousands of sessions. This can quickly add up to millions of sessions in a week. If one us using the standard session storage paradigm, it means your file system is filling up and slowing down Odoo. I normally store sessions in the DB, but we have the same issue there in that Odoo slows down because we now have millions of session records in the database.

To counter this, we constantly clear sessions from Odoo. A much better solution would be to have odoo-rpc-client simple respect the purpose of the Odoo session ID in the first place.

Also, the session ID for an established connection should be available as an attribute in the library. This will enable scripts to be able to use that session ID to make requests to Odoo controllers that require authentication, without having to write separate logic to re-authenticate to get a session ID.