Browser

Hi Mark,

The application is calling the Atmos API (Java binding) and not dealing with any timestamps. The call to atmos is made in background and the UI updated upon completion of the call. In this case however, it looks like even background call is timing out. Someone from the Atmos team might be able to throw more light on whether the timestamp is something enforced by Atmos. I could not find any API calls in the Java binding to make batch requests (i.e. to load only N objects per call).

Having said that the app does load objects with their metadata, which is not very efficient (and not necessary in this case) especially when dealing with the scale you have. It does that so that if an object has the 'objname' property set, the objname is displayed instead of the objectid. 

Based on your feedback and some observations from Raj, I will be updating the tool probably tomorrow and will include the call to only load object ids which will make it more efficient.

workspace folder - this is not a developer env artifact but is not a required folder for the app too - not a big concern if its not there.

Thanks,

Aashish

Does the tool have the ability to define a proxy setting?  It does not connect when on our work network, yet AtmosFox does not have a problem.  If I disconnect from our internal work network and use an external wireless it works fine.  The only difference I can think of is our internal network requires a proxy setting.

Thanks,

Jeff

Hi Jeff,

Unfortunately, the tool does not have the ability to specify Proxy settings.

Thanks,

Aashish