Thanks for the responses everyone. Amy: For some browsers yes, but nevertheless, it would be a nice capability for AIR to have. No idea how it works for other browser controls.
Wesley: The site I'm logging into is a third-party site that I have no control over. Martyn: This is with the mx:HTML control. I've noticed it uses a HTMLLoader (inherited from URLLoader), and that has a manageCookies property which when set to false, "allows me to manage cookies manually via header manipulation" according to the docs. Unfortunately, I can't work out how to hook into the loader to know when it is making requests, and the underlying request object so I can inject the headers. I'm not sending these requests manually with URLRequest and I can't because the user needs to be able to use the webpage via the mx:HTML control. 2009/3/31 Martyn Bowis <[email protected]>: > Have you considered using a single session, but separating out your > different user logins into separate child objects within that one session? > > eg: in a typical session, you might have a session object with the following > keys: > session.firstname > session.lastname > session.email > session.cart > ..., etc. > > So, why not instead use: > > session.user1.firstname > session.user1.lastname > session.user1.email > session.user1.cart > ..., etc. > and > session.user2.firstname > session.user2.lastname > session.user2.email > session.user2.cart > ..., etc. > > If the user is logging in from the same computer, then they are the same > person, but using separate objects for each of their logins/profiles like > the above may solve the problem you have. > > Kind regards, > Martyn > > > >
