> Ok. I've updated to the recent CVS snapshot today and
> this problem seems to have gone away, but only time will
> tell. However, I now have a small problem with the
> OneShot adapter and framesets. When I do a refresh,
> one or two of the three frames in the frameset fail
> to recognize the session... thus, one or two of my
> pages show the log-in screen (what happens when the
> session expires). This isn't such a bad bug, since
> I usually only debug one frame at a time with OneShot,
> and it seems to work well with the regular adapter.
I have similar problems with OneShot and pages that contain dynamically
generated images. This problem has been in OneShot for a long time. I just
avoid using OneShot when I'm developing pages with dynamic images :-)
The problem is that the session store assumes only one process is accessing
the session at a time, but when you're using OneShot, you can have multiple
processes stepping on each other.
The way to fix it would be to put some sort of mutex or file lock into
OneShot.cgi so that only one request is processed at a time. Should be
easy, but I'm not sure if it can be done in a platform-independent way.