I would like to "ping" the server to make sure the user's entered settings are correct after they configure Atmos in my system. Also to confirm simply that connectivity has been established before any other operations and during idle time.
I thought maybe a HEAD request to the ListObjects API, but I thought that has the potentialto create too much Server Side processing for nothing.
That's currently the best way to test connection and shared secret to Atmos Online.
We have a better way (not yet released though) that returns server version information. It requires shared secret and UID, so it's tests connectivity just like making a HEAD request to ListObjects without the server-side overhead.
You're correct, but in 1.2.5 and beyond, to get version information will require shared secret. Adam, I'm guessing, is interested in testing the complete communication including authentication, etc.
Yes, you are correct. However, I'd be curious to know what API call gets the Server version, is that available in the API today? If the call will enforce the authentication in the next server version, I'd prefer to only make one code change.
rbala1
222 Posts
432
0
Posted September 24th, 2009 14:00
Adam,
That's currently the best way to test connection and shared secret to Atmos Online.
We have a better way (not yet released though) that returns server version information. It requires shared secret and UID, so it's tests connectivity just like making a HEAD request to ListObjects without the server-side overhead.
Raj