David Benjamin

The proxy could staple server time and we use that to show a clock skew error message.

Yeah, it's labelled a proof-of-concept for a reason. :-) There's no UI. But it deletes the iframe in the callback. It also doesn't re-request tickets if already requested them once...

It deletes them upon getting a reply to the postMessage. If it never even gets one of those, then it probably doesn't. We could maybe listen for some appropriate event...

Note to self: be careful about where you display x_display with GTK's display. Follow Mozilla's logic here: http://mxr.mozilla.org/mozilla-central/ident?i=xtdisplay&filter=

#33 is possibly caused by something related to Xt compatibility code. Mozilla's GtkXtBin is already checked in. Perhaps investigate using that in nspluginwrapper too, instead of some custom code. (Could...

Wow. Thank you for the incredibly detailed report. I'll see if I can figure it out sometime (it's the end of term, so I'm a little busy these days). A...

> Regarding wrapper under Fedora, I think it's the default configuration. I _strongly_ recommend against doing that. There's really no benefit to running nspluginwrapper when both the plugin and the...

Actually you can't remove `gstdio.h`; it's intentionally separate so including `glib.h` does not pull `stdio.h` and everything and `g_chdir` is apparently defined in there. `gthread.h` should indeed be punted through....

Hrm. Looks like what's happening is that normally acroread actually sticks around as long the plugin does, but for some reason the wrapped one dies sooner. I suspect something is...

I don't believe so. The viewer hasn't crashed. Without nspluginwrapper, there are two processes involved: the browser/nppdf.so process and a slave acroread process. The acroread process is internal to nppdf.so....