Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

Re: Detecting early termination by client

by bibliophile (Parson)
on Apr 18, 2005 at 16:42 UTC ( #448941=note: print w/replies, xml ) Need Help??

in reply to Detecting early termination by client

I'd have the system automagically send back an email saying "I'm sorry, the transaction was aborted at your request" every time the user drops the connection... in the hope that eventually they'd learn :-)

Perhaps log a "starting transaction" and "transaction complete" at either end of the process, and then periodically scan the log for started-but-not-completed...?

Update: changed subject back to something relevent.

  • Comment on Re: Detecting early termination by client

Replies are listed 'Best First'.
Re^2: Detecting early termination by client
by enemyofthestate (Scribe) on Apr 19, 2005 at 01:35 UTC
    That is what I would like to do and I think should be the default behavior. After all if someone hits the close or stop button it's a good bet he wants the transaction halted. Unfortunately the boss does not agree.

    As a temporary measure I have taken to creating "emergency" logs for each transaction this particuar customer attempts. I spent today wrestling with SSL cetificate and Oracle AS 10g. Hopefully tomorrow I can load up teh CGI code and start experimenting.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://448941]
[marto]: Re: Monastery login over http
[Corion]: Veltro: This is due to the fact that one of our webservers doesn't have "our" https certificate but another https certificate. Work is underway (well, on my long, long to-do list) to switch even that server over to "our" certificate
[Veltro]: Corion OK, thanks. At least I understand it now.

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (10)
As of 2018-05-23 11:22 GMT
Find Nodes?
    Voting Booth?