Interoperability suggestions

[bochoven]

Dear dev,

Some people are looking eagerly at your efforts so they can reinstate the collection of warranty info to be used in munkireport-php. To make things easier, maybe also for you, I would like to give some suggestions:

• Use composer and packagist to embed your library. It makes life easier for people relying on your library. Packagist will automatically version the code when you release it.
• Allow for passing in the configuration variables, make the ini parser a fallback mechanism if the variables aren’t passed in. This will help programs to manage their own config mechanism.
• Make storing sessions in a database optional. I don’t think the original library had persistence for sessions and while it may speed up queries (does it?) it complicates inclusion - prevent db name collisions, db upgrades etc.
• Lastly, if you are going to use Composer, you might as well take advantage of the excellent monolog logging library

[bochoven]

Because of this, there needs to be some persistence to store the authorization token to be used over multiple requests.

Is it possible to request a new authorization token with each request? That way, you don’t need persistence

[Isaac-Duarte]

Hello Jesse! I'm currently in the process of writing my own implementation of the GSX API in C# for my company. I'm currently in the process working with my IT Department on getting access to the REST Api. I've created a base implementation as I do not have any idea of endpoints and such. My question is for the one-time authentication code. How is that specifically obtained? I know you mentioned users can manually retrieve the activation token from Apple Is this a text message type thing like logging into GSX? Thank you! I am just wanting to get an Idea so I can start writing some code beforehand to speed up the process.

[Isaac-Duarte]

Okay thanks man I appreciate your response!