Hi Brad, I've used the iframe solution on a project, as well. It worked for me. However, I think there are some drawbacks. You loose visual control over what's going on in the hidden iframe. I loaded .jsp into the iframe that wouldn't even compile and didn't notice, because I didn't see the compiler error. :-(
All in all it feels more like a workaround than a solution. It adds complexity to debugging and you have to rely heavily on JavaScript - another source of trouble, to be sure. Do you have to support multiple user agents / versions? Some things you should ask yourself: # What happens if the user decides to abort the transaction? (How are you going to delete entries form DB?) # Does it *really* make sense to do a trip to the db for *every* time the use clicks a checkbox? # What happens if user that clicks faster than your average request/response roundtrip? That's not too hard to imagine. I think you're buying into more problems than you solve, actually. Just my penny's worth. Regards, Nils This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
