Yes that's exactly it.
I have thought of a work around that uses a sort of backwards AJAX where I open a connection from the app, the web page tells the server when something is clicked and then the server responds to the applications AJAX call, which then opens a new connection. It's complicated and I can see lots of issues to work around, not the lease of which is going to be linking two independent AJAX calls from a stateless web server grrrr, so i'd rather read the DOM if I can.
Currently OSAkit is working really well and i'm really chuffed with it save for the Firefox issue Sphinx knows about, i'm doing a demonstration from a sandboxed webpage to my boss and the CEO on Monday so i've got a busy weekend to get an application up and working and polished, if not yet feature rich - thank Blitz for it's rapid development speed, i've already solved most of the hurdles :)
I have thought of a work around that uses a sort of backwards AJAX where I open a connection from the app, the web page tells the server when something is clicked and then the server responds to the applications AJAX call, which then opens a new connection. It's complicated and I can see lots of issues to work around, not the lease of which is going to be linking two independent AJAX calls from a stateless web server grrrr, so i'd rather read the DOM if I can.
Currently OSAkit is working really well and i'm really chuffed with it save for the Firefox issue Sphinx knows about, i'm doing a demonstration from a sandboxed webpage to my boss and the CEO on Monday so i've got a busy weekend to get an application up and working and polished, if not yet feature rich - thank Blitz for it's rapid development speed, i've already solved most of the hurdles :)