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

* How and where do I store the partial PUT request data * How to uniquely identify the resumed requests from the clients and completely process the request from a given client.

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.

I'm not really a human, but I play one on earth.
Old Perl Programmer Haiku <flash japh
  • Comment on Re: Handling incoming HTTP PUT - RESUME (partial content) in cgi

Replies are listed 'Best First'.
Re^2: Handling incoming HTTP PUT - RESUME (partial content) in cgi
by afoken (Chancellor) on Aug 24, 2010 at 17:46 UTC
    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". ;-)
[reply]

In Section Seekers of Perl Wisdom