next »

[perkiset]

Well, I can only frustrate I'm afraid.

I built some automated systems that pulled against my SSL Ajax systems . I tried different versions of Windows, different processor loads, faster and slower connections, multiple instances of IE open at the same time, being the first thing done and clicking after a session had been open for a long time.

Same randomness, no matter what.

The worst part, was that I'd go, like, 3000 iterations with nothing and think I was on to something, and then POOF it'd be back.

That's why I write the XHR I referenced earlier - I needed a way to securely send data to an AJAX app.

My most recent retail stuff is using more JS, then POSTs and finally an iFrame for the moment of truth. Works like this: I do almost all verification of data via JS on the local client. When I like it there, I POST it up to the server (checking again, of course) but pushing everything into a session so that it's usable. (This part may be done several times, based on what the client system needs to do). When I actually initiate a transaction, I use a hidden iFrame so that I can continue with a local animation (to let the client know something's going on) which returns a small script to bounce the client when a transaction is complete or not.

I use AJAX for anything that is unsecure, or backoffice systems where I can control which browser is used. It's perfect - fast and accurate - if I can control the browser.