Originally Posted by
gordonb3
I don't think what you intend to do can work. Creating the object/instance will cause the "__init_" procedure to be executed. Of course a failed login due to the imposed session limit does not keep you from still inserting the auth key from the previous session, but then you still need to call the routine that fetches your userId that is required to query the installation info and status.
Following the logic, __init_ calls _login (which you should prevent). _login calls _basic_login (which performs the actual login and stores the auth key), then calls get user info (this you must do) and finally a get installation info which is probably pointless because you are likely to do a get full installation info call in your script.
Edit: of course you could also cache the user ID and possibly other static info as well. Whether that simplifies the challenge at hand or complicates even more is a bit hard to answer.