Prevent Drive error when the socket is already in use by another application

This is the scenario which could happen, even if it depends on an external app

1) run Drive => the PID for the Drive process is stored in nxdrive_qt.pid
2) when files are synchronized or when Direct Edit is used, Drive will use a port to open a socket (based on the PID + port?) during Drive actions
3) then another application is started and the Operating System could assign the same socket to this app (because it is free when Drive is not doing anything)
4) if Drive is used now, it will try to use the previous socket which is now busy (used by the other app) and Drive will throw errors

Could we have a more robust system where :

• Drive keeps the socket (I don't know if it's feasible and/or if it is a best practice)
• Drive tries to use another socket if the default one (based on PID+port) is already used by another app