Recent Blog Comments By Ezra Parker

One final point worth clarifying here (at the risk of beating a dead horse): Without any session cookies set, if you hit the demo multiple times within the "sleeping" window, then *every* request will fire OnSessionStart, and each will receive a new set of session identifier cookies, as they are al... read more »

FWIW, the relevant Firefox setting appears to be network.http.use-cache, which defaults to true. If I set this to false, then the second frame's request for the same filename does not wait for the first to complete, and the error is produced. This would seem to make sense, as it looks like the brow... read more »

@Anthony, you mean in another frame? If I add an image in a third frame, that request goes through immediately, while the first two frames that are requesting the same .cfm file both wait for the delayed session instantiation to complete. If I instead use two different files for the first two fram... read more »

@Ray, there are most definitely two sessions created when starting without cookies, and only one when the cookies exist. My relevant FF settings are: network.http.pipelining: false network.http.pipelining.maxrequests: 4 These are both the defaults, and setting network.http.pipelining to true did ... read more »

And some of this evidently has to do with the browser's behavior, as if I use two different but identical files for the frame contents (e.g., frame1.cfm and frame2.cfm), I consistently receive an error on the second frame when reinitializing with the cookies persisted. So it does indeed appear that... read more »

@Anthony, that depends... If I clear the session cookies, then hit the test page, two sessions are created, and both do indeed time out. The latter set of cookies "wins", however, and the first session is disconnected from the browser. Once the cookies exist in the browser, then only one session i... read more »

@Ray, regarding the frameset issue, using a .cfm would indeed solve that particular angle (and I most certainly agree that they are just a bad idea regardless). As Ben noted, however, it is possible for user behavior to produce concurrent requests (by double-clicking links or re-submitting forms, fo... read more »

@Anthony, I'm aware of the typical race condition scenario, but what threw me a bit here is the fact that in Firebug, it appeared to me that the second request was queued behind the first when the frames were both calling the same inner file. It did not look like the second request was initiated un... read more »

@Ray, I'm running CF in a terminal window, and logging the session and application timeouts so I can see exactly when they occur. If I refresh after session timeout and before application timeout, I get the error (I set the timeout values to 10 and 30 seconds, respectively). Once the application ti... read more »

If I hit the frameset without session cookies stored (in FF 3 on Linux, BTW), then I am observing the same results as Ray -- the second frame waits for the first to complete, no error is produced, and, interestingly, each frame has a unique session. If I retain the session cookies and allow the ses... read more »

Hi, Ben. I had just downloaded your POI tags this last week to try out ( very cool, by the way), and ran into this issue. I believe I have figured out a workaround, which is to use the findFont method to see if the formatting you wish to use already exists, instead of calling CreateFont each time. ... read more »