Why Connection class sets the cert_path, team_id and key_id during its initialization? If I understand it correctly, it only uses these attributes for sending push notification and it has nothing to do with connection and connection_pool. This creates a problem that you can't use the same connection_pool and connection for sending push notifications to different apps that belong to different teams, organizations, etc. Is it possible to pass these attributes as parameters to push method instead?
I understand current implementation might be motivated by the need to set the SSL context during initialization but when auth_method is token, this seems like an unnecessary limitation.
Why Connection class sets the
cert_path
,team_id
andkey_id
during its initialization? If I understand it correctly, it only uses these attributes for sending push notification and it has nothing to do with connection andconnection_pool
. This creates a problem that you can't use the sameconnection_pool
andconnection
for sending push notifications to different apps that belong to different teams, organizations, etc. Is it possible to pass these attributes as parameters topush
method instead?I understand current implementation might be motivated by the need to set the
SSL
context during initialization but whenauth_method
istoken
, this seems like an unnecessary limitation.