DFC extended transaction

Im writing a client java application which uses DFC to upload files to the repository.

In order to preserve memory on the client each file is uploaded when a user selects it, or when a user via. twain scans a picture using a scanner.

So to make sure all files are uploaded or non are uploaded i would like to begin a transaction (beginTransaction) when the first file is uploaded and then commitTransaction when the user is finished uploading the data. If something fails i would then of course use rollbackTransaction.

My problem is the 5 minute timeout, so if a user is a bit slow and have not interacted (uploaded a file or completed the entire upload) with the system for 5 minutes the server closes the session and the entire upload is binned.

Any1 has any thoughts on this. I know im not supposed to but i hold on to the session i get from begintransaction.

Im not sure if its the entire design thats **** or my way of implementing it.

Can a beginTransaction scope several getSession() releaseSession() calls.

Any1?

Find more posts tagged with

Comments

lastnitescurry

Worked on a scanning project last Summer... scaning interface was not my baby but I was involved in testing it... I specfically tested how it would handle users leaving the process after a scan or two and then walking away for lunch!!! Maybe lunch not feasiable but in that site long run phone calls that had to be taken were

Suggest you store the files on client PC, and only upload to repository when user is happy.

Not saying your current design is **** but I think it would also fail under

* failure in repository network connection, repository shut down, or database network connection / shutdown

ThomasSSE

Thanks for the reply..

Storing the files locally might be the way to go. The only problem i have with that sollution is that we are not allowed to store the files locally since they contain patient-sensitive material. But I might overcome that problem with the right arguments i think.