Re^3: Forcing output to a browser when perl is busy

IMHO the Javascript approach is the least interesting route. What if:

The user disabled Javascript
The connection to the server really did fail. This is something people visiting Perlmonks should be familiar with... ;-) You're only going to annoy users, who'll lose posts this way.

In my eye, using a unique (session) id per post, be it submitted or not, is the only way. The server can then choose to either reject posts with the same id, or use it to update an earlier submission (by the same user!)

You can combine that with a quick response page, which might even automatically reload after a short while. See merlyn's WebTechniques column "Search in progress" page for some ideas.

Comment on Re^3: Forcing output to a browser when perl is busy

Replies are listed 'Best First'.
Re^4: Forcing output to a browser when perl is busy by Anonymous Monk on Jul 20, 2004 at 01:40 UTC
True, everything has a gotcha. Thus far, the Javascript has taken care of the problem. However, it's not perfect. I'm in the process of porting all this code for mod_perl and re-writing major sections. Doing the redirect would be simpler to add at that time. Assigning a unique id would be the best solution; however, the message and the reply dialogue are just html pages, so it's not possible as far as I know without a fairly major architectural change.	[reply]

Replies are listed 'Best First'.

Re^4: Forcing output to a browser when perl is busy
by Anonymous Monk on Jul 20, 2004 at 01:40 UTC

True, everything has a gotcha. Thus far, the Javascript has taken care of the problem. However, it's not perfect. I'm in the process of porting all this code for mod_perl and re-writing major sections. Doing the redirect would be simpler to add at that time. Assigning a unique id would be the best solution; however, the message and the reply dialogue are just html pages, so it's not possible as far as I know without a fairly major architectural change.

[reply]