You might want to look at CGI::Session, it stores all transactions in a database, and you probably can use that to identify resumed requests by examining the last transaction.
Good idea, except that CGI::Session uses algorithms for the session ID that may cause collisions. See Re^4: Randomness encountered with CGI Session.
Alexander
In reply to Re^2: Handling incoming HTTP PUT - RESUME (partial content) in cgi
by afoken
in thread Handling incoming HTTP PUT - RESUME (partial content) in cgi
by chanakya
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |