So I'm making a library wrapping a Google REST API.
And the way I'm doing the OAUTH2 authorization is by starting a local server, opening the login website for the user to login and receiving the response in the local server. After that I don't really need the local server anymore.
Is there a way to stop it? maybe having the code in a class, and destroying the instance after using it somehow?
Or, are there any disadvantages for leaving it running all the time? (apart from having an unnecessary port opened)
And the way I'm doing the OAUTH2 authorization is by starting a local server, opening the login website for the user to login and receiving the response in the local server. After that I don't really need the local server anymore.
Is there a way to stop it? maybe having the code in a class, and destroying the instance after using it somehow?
Or, are there any disadvantages for leaving it running all the time? (apart from having an unnecessary port opened)