in reply to Re: Handling incoming HTTP PUT - RESUME (partial content) in cgi
in thread Handling incoming HTTP PUT - RESUME (partial content) in cgi

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

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
  • Comment on Re^2: Handling incoming HTTP PUT - RESUME (partial content) in cgi