Maybe ... in javaSessionFail just print and set a flag, Then return because of the error condition. The calling function might then return because of the error, and so on, unwinding the stack all the way back to html. So there was an error but cw->jss is still there. in the SwitchCompartment macro, if js is dead then return, as we do today, but if it is still there and the abort flag is set then destroy context and set jss = null and return.
Everything would unwind and free properly, and the js context would go away, perhaps on the next call. Maybe that would keep things from becoming a mess. Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
